On Feb 25, 2013, at 15:42, [email protected] wrote: > Revision: 103433 > https://trac.macports.org/changeset/103433 > Author: [email protected] > Date: 2013-02-25 13:42:58 -0800 (Mon, 25 Feb 2013) > Log Message: > ----------- > devel/boost: blacklist clang on i386 (#38157) > > Modified Paths: > -------------- > trunk/dports/devel/boost/Portfile > > Modified: trunk/dports/devel/boost/Portfile > =================================================================== > --- trunk/dports/devel/boost/Portfile 2013-02-25 20:38:21 UTC (rev 103432) > +++ trunk/dports/devel/boost/Portfile 2013-02-25 21:42:58 UTC (rev 103433) > @@ -46,6 +46,11 @@ > # > (http://en.gentoo-wiki.com/wiki/Safe_Cflags/Intel#Intel_Core_Solo.2FDuo.2C_Pentium_Dual-Core_T20xx.2FT21xx) > # to fix broken 32-bit builds as per > (https://trac.macports.org/ticket/35172). > reinplace "s|-march=i386|-march=prescott|g" > ${worksrcpath}/tools/build/v2/tools/gcc.jam > + # 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) > + if {[lsearch ${build_arch} i386] != -1} { > + compiler.blacklist clang > + }
Only Apple clang is affected? Not MacPorts clang? _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
