On Tue, Apr 10, 2012 at 12:29:49AM +1000, Joshua Root wrote:
> On 2012-4-9 22:55 , Jack Howarth wrote:
> > 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.
>
> Nothing in base has changed to affect this. You changed the pymol port
> to declare an empty build phase 6 weeks ago, so of course setting
> build.env doesn't do anything useful.
>
> - Josh
Josh,
Pymol upstream changed their build procedure in 1.5 so that they no longer
support...
python setup.py build
python setup.py install
but only...
python setup.py install
which both compiles and installs pymol. So I guess I may need to have an
explicit
install phase instead of using the default python port one in order to pass CC
and CXX in front of the 'python2.x setup.py install' if build.env isn't
available
in the install phase.
Jack
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
