On Sep 14, 2012, at 00:33, Dan Ports <[email protected]> wrote: > On Thu, Sep 13, 2012 at 10:39:14PM -0700, Jeremy Huddleston Sequoia wrote: >> The problem seems to be that some of MacPorts' gcc compilers have been built >> with --enable-fully-dynamic-string and others haven't. gcc44 and gcc45 are >> built with --enable-fully-dynamic-string and gcc46, gcc47, and gcc48 aren't, >> so gcc44 and gcc45 aren't compatible with the libstdcxx that is built from >> gcc47 because of this difference. > > Yes, exactly. The reason this is a problem is that rebuilding the > compiler without --enable-fully-dynamic-string isn't enough. The > binaries built with that compiler have to be rebuilt too.
Yep, so we're going to need to revbump those ports. This onion just keeps getting bigger and bigger. If I knew how deep this libstdc++ issue was going to go, I would've left well enough broken ... =/ Oh well, at least things will be in a better state when this is all over with. Hopefully a revbump of relevant ports was done after gcc46 dropped --enable-fully-dynamic-string, so we can just mine a followup commit from that change for a list of ports to bump. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
