[112423] trunk/dports/python/py-healpy/Portfile

Ryan Schmidt ryandesign at macports.org
Wed Oct 23 00:11:21 PDT 2013


On Oct 22, 2013, at 10:24, aronnax at macports.org wrote:

> Revision: 112423
>          https://trac.macports.org/changeset/112423
> Author:   aronnax at macports.org
> Date:     2013-10-22 08:24:20 -0700 (Tue, 22 Oct 2013)
> Log Message:
> -----------
> py-healpy: blacklist broken llvm-gcc42 compiler

Remember to include a reference to the ticket number in the commit message.


> Modified Paths:
> --------------
>    trunk/dports/python/py-healpy/Portfile
> 
> Modified: trunk/dports/python/py-healpy/Portfile
> ===================================================================
> --- trunk/dports/python/py-healpy/Portfile	2013-10-22 14:00:01 UTC (rev 112422)
> +++ trunk/dports/python/py-healpy/Portfile	2013-10-22 15:24:20 UTC (rev 112423)
> @@ -32,7 +32,10 @@
>     default_variants    +openmp
> 
>     variant openmp description "enable OpenMP parallel acceleration" {
> -        compiler.blacklist-append *clang*
> +        # FIXME: llvm-gcc42 is broken, https://trac.macports.org/ticket/40713
> +        # Only clang really needs to be blacklisted
> +        compiler.blacklist *gcc-4.2 *clang*
> +        compiler.fallback macports-gcc-4.8 macports-gcc-4.7 macports-gcc-4.6 macports-gcc-4.5 macports-gcc-4.4 macports-gcc-4.3

The ticket only talks about MacPorts llvm-gcc-4.2 being a problem… why blacklist FSF GCC as well?




More information about the macports-dev mailing list