On Nov 9, 2014, at 12:13 PM, Thomas Ruedas <[email protected]> wrote: > The only thing a web search turned up that seemed directly related to this > problem was http://trac.macports.org/ticket/45637, but it didn't really help > me, because I don't know how to apply this fix. Isn't there an official fix > for this problem?
There is now. Run selfupdate in half an hour or so to pull down the new port. https://trac.macports.org/changeset/127972 vq _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
