should cxx11 1.1 PortGroup also blacklist older clangs (< 600, say) during libc++ builds?

Ken Cunningham ken.cunningham.webuse at gmail.com
Sat Aug 12 22:07:49 UTC 2017


I’m sorry - retract this. I see there is already a section where this is done that I had glossed past before.

I’ll have to look into why I still need to fiddle with this sometimes.

Sorry for noise.

Ken


> On Aug 12, 2017, at 3:02 PM, Ken Cunningham <ken.cunningham.webuse at gmail.com> wrote:
> 
> The libstdc++ section of this portgroup forces clang 4.0, and the PPC section forces gcc6. Those cover almost all current port compiler requirements.
> 
> But there is still a hole in the libc++ section, and it happens often enough that older clangs (< 600 or so) have to be blacklisted on older systems separately.
> 
> It would seem consistent with the purpose of the Portgroup that this might be included in the libc++ section to save this coming into each Portfile separately.
> 
> Something like this:
> 
> ====
> 
> } else {
>    # GCC compilers can not use libc++
>    compiler.blacklist-append   *gcc*
> 
>    compiler.blacklist-append   { clang < 600 }
> 
> }
> 
> ======
> 
> would probably do it for now. (That could be bumped to 800 - or more - rather easily in the future when that is needed).
> 
> 
> Ken



More information about the macports-dev mailing list