On Sun, Apr 08, 2012 at 12:48:14PM -0400, Jeremy Lavergne wrote:
> > The fact that, on Lion, MacPorts 2.0.4 installs perl/python that defaults
> > to llvm-gcc-4.2 made me
> > suspect that the binary packages installed on Lion were built with SL. If
> > not, this brings up the
> > question of why the Lion build bots are on such an old Xcode that they
> > don't default all of the
> > package builds to clang. Perhaps they should be updated to Xcode 4.3.2 and
> > a bulk rebuild of the
> > MacPorts package set started.
>
> Pretty sure we just started running the first builds on the Lion buildbot
> this weekend.
>
> I don't know their configurations, but it's entirely possible that it has a
> non-current Xcode. wms is doing pretty much all the work on setting up the
> buildbots. Maybe we can get a wiki page setup with the configuration
> information for each buildbot.
>
I am also having trouble getting the compiler variants in pymol to work under
macports 2.0.4.
Using...
sudo port -d install pymol +gcc45
still builds pymol against clang locally. 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?
Jack
ps I am trying to test a pymol build against llvm-gcc-4.2 (with everything else
built
with clang as expected). Changing...
--- Portfile.orig 2012-04-08 15:10:54.000000000 -0400
+++ Portfile 2012-04-08 15:28:08.000000000 -0400
@@ -6,6 +6,7 @@
name pymol
version 1.5
+revision 1
categories science
maintainers bromo.med.uc.edu:howarth
description Molecular graphics system
@@ -20,7 +21,7 @@
master_sites sourceforge
fetch.type svn
svn.url https://pymol.svn.sourceforge.net/svnroot/pymol/trunk/pymol
-svn.revision 3983
+svn.revision 3996
worksrcdir pymol
depends_lib port:freetype port:libpng port:python26 port:py26-pmw
port:py26-numpy port:py26-scipy port:mesa port:glew port:py26-tkinter
port:freeglut
@@ -61,7 +62,9 @@
}
pre-build {
- build.env CC="${configure.cc}" CXX="${configure.cxx}"
+# build.env CC="${configure.cc}" CXX="${configure.cxx}"
+ python.add_archflags no
+ build.env CC="llvm-gcc-4.2" CXX="llvm-g++-4.2"
}
build {
doesn't cause llvm-gcc-4.2 to be used nor does any of the gcc4x variants work.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
