On Apr 21, 2013, at 2:16 PM, Jean-François Caron <[email protected]> wrote:
> Hello, while doing a routine selfupdate+upgrade, perl5.12 failed to build. I > found a ticket that seemed to have a similar problem > (http://trac.macports.org/ticket/36444) This is the actual problem. http://trac.macports.org/ticket/36438 > and tried the solution of rebuilding libstdcxx with +universal, but perl5.12 > still fails with the same error. Something is wrong then. Maybe your universal libstdcxx is not actually activated, or perhaps you need to clean perl5.12 before trying again. As I've posted several times to this mailing list (and at http://trac.macports.org/ticket/38858#comment:3) in the past couple of days, the workaround is to force-deactivate libstdcxx for the duration of the upgrade. % sudo port clean perl5.12 % sudo port -f deactivate libstdcxx % sudo port upgrade perl5.12 % sudo port activate libstdcxx vq _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
