On 2012-2-17 15:38 , Eric Cronin wrote: > The main problem I ran in to is that a number of our ports cache the compiler > they were built with internally (libtool, python, apr), and then a number of > other ports interrogate those first set of ports to get the paths of tools to > use, resulting in attempts to compile using /Developer/.../llvm-g*-4.2, which > no longer exists. This is probably a bug with the dependent ports from a > MacPorts angle, since we want the compiler the Portfile/base specifies used, > not what 'apr-1-config --cc' returns. Force reinstalling the ports caching > paths to the toolchain allowed the remaining ports to be built. Some variant > of the migration upgrade steps is probably required to make sure nothing has > /Developer paths stored away…
This isn't a problem with libtool at least since the build systems still obey CC in the configure environment. You do get problems if they then neglect to use the appropriate --tag argument when invoking libtool, but that can and should be patched. - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
