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

[ryandesign at macports.org]

Revision: 126002
          https://trac.macports.org/changeset/126002
Author:   ryandesign at macports.org
Date:     2014-10-01 13:41:33 -0700 (Wed, 01 Oct 2014)
Log Message:
-----------
boost: consolidate some blacklist entries and remove blacklist entries for gcc 4.2, fixing the build on Leopard and Tiger (#44918)

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

Modified: trunk/dports/devel/boost/Portfile
===================================================================
--- trunk/dports/devel/boost/Portfile	2014-10-01 19:23:35 UTC (rev 126001)
+++ trunk/dports/devel/boost/Portfile	2014-10-01 20:41:33 UTC (rev 126002)
@@ -74,9 +74,7 @@
 # clang++ produces broken boost libraries (https://trac.macports.org/ticket/31525)
 # If Apple's clang is used on 32-bit systems, it seems to silently ignore the '-march=i386' flag.
 # (https://trac.macports.org/ticket/38157)
-# gcc <= 4.2 does not support TR1 result_of protocol
-# https://trac.macports.org/ticket/39809
-compiler.blacklist {clang < 421} macports-clang-2.9 macports-clang-3.0 llvm-gcc-4.2 macports-llvm-gcc-4.2 apple-gcc-4.2 gcc-4.2 gcc-4.0 apple-gcc-4.0 gcc-3.3
+compiler.blacklist {clang < 421} macports-clang-2.9 macports-clang-3.0 *llvm-gcc-4.2 *gcc-4.0 gcc-3.3
 
 # 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-changes/attachments/20141001/17dab104/attachment.html>