macports 2.0.4 breaks the usage of clang on Xcode 4.3.2
Jack Howarth
howarth at bromo.med.uc.edu
Mon Apr 9 05:55:00 PDT 2012
On Sun, Apr 08, 2012 at 08:34:57PM -0400, Jeremy Lavergne wrote:
> > Also non-sensical values like...
> >
> > sudo port -d install pymol +gcc49
> >
> > don't produce an error. Is that expected behavior for the error to be
> > silently ignored by port?
>
> Variants are trickle down, so if a port doesn't have a variant it isn't actually an error.
>
My concern is that the usage of...
configure.compiler macports-gcc-4.5
and
build.env CC="${configure.cc}" CXX="${configure.cxx}"
appears to be broken now. This was recommended to me as the appropriate way to handle
the compiler variants...
http://trac.macports.org/wiki/PortfileRecipes#gcc
This used to work such that...
sudo port -d install pymol +gcc45
would compile pymol with the gcc-mp-4.5 compiler but current port in MacPorts 2.0.4
seems to have broken this feature and, under Xcode 4.3.2, the clang compilers are
always used.
Jack
More information about the macports-dev
mailing list