Yeah that's fine with me... FYI...I just tried that hack mentioned in the bug, but its not getting past configure, so I am not sure what good changing gcc and g++ to force -m32 is gonna do.
:/ On Fri, Mar 16, 2012 at 1:30 AM, Ryan Schmidt <ryandes...@macports.org>wrote: > On Mar 16, 2012, at 01:23, Jeff Singleton wrote: > > > Yep that bug is way closer to correctness … now I think we are on to > something. > > I've set up a separate MacPorts prefix, in which I'll try to build all > p5.12 ports with a non-standard build_arch. That should help me determine > whether arch ignorance is specific to individual port, or something we need > to correct in the perl5 portgroup. It may take awhile to build. :) > > > > I just tried that 0.50.2 version and it does the same thing…so I > wouldn't rush pushing that one into the tree just yet. > > I already committed it, since based on the above I don't think the > intltool port itself has anything to do with the failure. > > >
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
