compiler.blacklist

Ryan Schmidt ryandesign at macports.org
Fri Jun 29 03:28:36 PDT 2012


On Jun 29, 2012, at 04:18, jmr at macports.org wrote:

> Revision: 94768
>          https://trac.macports.org/changeset/94768
> Author:   jmr at macports.org
> Date:     2012-06-29 02:18:08 -0700 (Fri, 29 Jun 2012)
> Log Message:
> -----------
> ccrypt: blacklist clang (see #32377)
> 
> Modified Paths:
> --------------
>    trunk/dports/security/ccrypt/Portfile
> 
> Modified: trunk/dports/security/ccrypt/Portfile
> ===================================================================
> --- trunk/dports/security/ccrypt/Portfile	2012-06-29 08:06:59 UTC (rev 94767)
> +++ trunk/dports/security/ccrypt/Portfile	2012-06-29 09:18:08 UTC (rev 94768)
> @@ -34,6 +34,11 @@
>                         sha1    5ad1889c71be905c3004c80dc011948c9c35c814 \
>                         rmd160  2e7ec037dcfab82ad6963b8644a52017ac6c003e
> 
> +depends_lib             port:gettext
> +
> +# test fails, ticket #32377
> +compiler.blacklist      clang


I assume this new compiler.blacklist feature replaces some or all of our previous recommendations for how to override the default compiler? Could you or someone who understands the new feature update our recipe? Thanks.

https://trac.macports.org/wiki/PortfileRecipes#compiler



More information about the macports-dev mailing list