On Feb 5, 2008 6:14 PM, Ryan Schmidt <ryandesign@macports.org> wrote:

The problem has not been worked around. The bug is still open:

http://trac.macosforge.org/projects/macports/ticket/14144

The problems that were worked around were the "unable to infer tagged
configuration" bug affecting apache2, mjpegtools and possibly others.
These were fixed by bumping the revision of apr and libtool to force
their rebuild.

The libidl bug is a different and unrelated bug. libidl is
unmaintained so someone will have to volunteer to figure out what's
breaking, and how to fix it. Actually, Tod Morrison just posted in
the bug that he found a reason why it's failing, and a workaround,
but not yet a fix that we can apply to the portfile.


howsomever, it upgraded just fine two days ago: I assumed it was fixed. 

The following ports are currently installed:
  libidl @0.8.10_0 (active)
 



--
Paul Beard / www.paulbeard.org/
<paulbeard@gmail.com/paulbeard@gmail.com>