[110453] trunk/dports/security/tor-devel/Portfile

Ryan Schmidt ryandesign at macports.org
Sat Aug 31 00:48:22 PDT 2013


On Aug 31, 2013, at 02:05, jeremyhu at macports.org wrote:

> Revision: 110453
>          https://trac.macports.org/changeset/110453
> Author:   jeremyhu at macports.org
> Date:     2013-08-31 00:05:19 -0700 (Sat, 31 Aug 2013)
> Log Message:
> -----------
> tor-devel: Remove blacklisting.  It was just wrong.
> 
> Modified Paths:
> --------------
>    trunk/dports/security/tor-devel/Portfile
> 
> Modified: trunk/dports/security/tor-devel/Portfile
> ===================================================================
> --- trunk/dports/security/tor-devel/Portfile	2013-08-31 06:57:15 UTC (rev 110452)
> +++ trunk/dports/security/tor-devel/Portfile	2013-08-31 07:05:19 UTC (rev 110453)
> @@ -32,11 +32,6 @@
>                     port:openssl \
>                     port:zlib
> 
> -# http://llvm.org/bugs/show_bug.cgi?id=15201
> -if {[variant_isset universal]} {
> -    compiler.blacklist-append clang macports-clang-2.9 macports-clang-3.0 macports-clang-3.1 macports-clang-3.2 macports-clang-3.3
> -}

It wasn't wrong when I added it in r102737. clang crashed when building universal, so I blacklisted it. I'm able to reproduce that error if I downgrade the port back to that revision and try to use clang.

The problem appears to have been corrected by updating tor-devel to 0.2.4.12-alpha in r105521, so the blacklisting is no longer necessary.



More information about the macports-dev mailing list