[108750] trunk/dports/devel/boost/Portfile
ryandesign at macports.org
ryandesign at macports.org
Wed Jul 31 15:01:32 PDT 2013
Revision: 108750
https://trac.macports.org/changeset/108750
Author: ryandesign at macports.org
Date: 2013-07-31 15:01:32 -0700 (Wed, 31 Jul 2013)
Log Message:
-----------
boost: clang from Xcode < 4.4 doesn't build the port on x86_64 either; blacklist it always, and use the compiler_blacklist_versions portgroup to do so instead of sniffing the Xcode verson; also blacklist macports-llvm-gcc-4.2 which fails just like Xcode's llvm-gcc-4.2
Modified Paths:
--------------
trunk/dports/devel/boost/Portfile
Modified: trunk/dports/devel/boost/Portfile
===================================================================
--- trunk/dports/devel/boost/Portfile 2013-07-31 21:44:02 UTC (rev 108749)
+++ trunk/dports/devel/boost/Portfile 2013-07-31 22:01:32 UTC (rev 108750)
@@ -2,6 +2,7 @@
# $Id$
PortSystem 1.0
+PortGroup compiler_blacklist_versions 1.0
name boost
version 1.54.0
@@ -60,10 +61,7 @@
# (https://trac.macports.org/ticket/38157)
# gcc <= 4.2 does not support TR1 result_of protocol
# https://trac.macports.org/ticket/39809
-compiler.blacklist macports-clang-2.9 macports-clang-3.0 llvm-gcc-4.2 apple-gcc-4.2 gcc-4.2 gcc-4.0 apple-gcc-4.0 gcc-3.3
-if {[vercmp $xcodeversion 4.4] < 0 || [lsearch ${build_arch} i386] != -1} {
- compiler.blacklist-append clang
-}
+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
# 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: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20130731/03c14fe6/attachment.html>
More information about the macports-changes
mailing list