If you had read my entire email you would have seen that I have tried building (rebuilding) everything again.
I guess the reason I am asking for what I am … is that (for example), the less popular HomeBrew for OS X offers methods for using GCC (a switch for 'install --use-gcc') as my preferred compiler, and not defaulting to Apple's default compiler. I just was hoping that the maintainers for the overall MP sources would create something similar. If you are able to build Pango weekly…then you must be doing something differently that I. Possibly not using the same Arch/Platform or possibly you customize your Portfile prior to building. My issues stem from the default Portfile and using MacPorts pretty much as is, with some minor variant changes and setting x86_64 only as my build_arch. (Though I have tried i386 and get the same results). Jeff On Mon, Apr 16, 2012 at 5:33 AM, Jeremy Lavergne <jer...@lavergne.gotdns.org > wrote: > > There simply HAS to be some way of forcing Macports to use the compiler > that I want to use and not argue and not make changes whenever and just do > what I tell it to. > > There is a default compiler option in trunk, but no one is having the > issues you are (I build pango weekly to make installers for PSPP). > Have you tried rebuilding all your packages? > >
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users