[98466] trunk/dports/devel/boost/Portfile

adfernandes at macports.org adfernandes at macports.org
Fri Oct 5 14:48:41 PDT 2012


Revision: 98466
          http://trac.macports.org//changeset/98466
Author:   adfernandes at macports.org
Date:     2012-10-05 14:48:41 -0700 (Fri, 05 Oct 2012)
Log Message:
-----------
devel/boost: ensure that user-config.jam is always written (#36485)

Modified Paths:
--------------
    trunk/dports/devel/boost/Portfile

Modified: trunk/dports/devel/boost/Portfile
===================================================================
--- trunk/dports/devel/boost/Portfile	2012-10-05 21:30:34 UTC (rev 98465)
+++ trunk/dports/devel/boost/Portfile	2012-10-05 21:48:41 UTC (rev 98466)
@@ -61,6 +61,12 @@
     compiler.blacklist-append clang
 }
 
+# It turns out that ccache and distcc can produce boost libraries that, although they
+# compile without warning, have all sorts of runtime errors especially with pointer corruption.
+# Since most people will now use MacPorts' pre-compiled boost, this should not be a problem.
+configure.ccache    no
+configure.distcc    no
+
 configure.cmd       ./bootstrap.sh
 configure.args      --without-libraries=python \
                     --without-libraries=mpi \
@@ -68,15 +74,13 @@
 
 configure.universal_args
 
-# It turns out that ccache and distcc can produce boost libraries that, although they
-# compile without warning, have all sorts of runtime errors especially with pointer corruption.
-# Since most people will now use MacPorts' pre-compiled boost, this should not be a problem.
-configure.ccache    no
-configure.distcc    no
+post-configure {
 
-post-configure {
     reinplace -E "s|-install_name \"|&${prefix}/lib/|" \
         ${worksrcpath}/tools/build/v2/tools/darwin.jam
+
+    write_jam "using darwin : : ${configure.cxx} ;"
+
 }
 
 # Although bjam can supposedly use parallel builds, it has random failures. See #28878 and #23531.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20121005/30b8eece/attachment.html>


More information about the macports-changes mailing list