error: thread-local storage is not supported

[Chris Jones]

yes, just go with manually blacklisting compilers as required...

Might also be useful to submit a github issue against base, to discuss 
improving things there.

Chris

On 21/11/2019 1:30 pm, Renee Otten wrote:
> Thank you Josh.
> 
> Unfortunately that doesn’t help as the same compilers are selected on 
> OSX 10.8-10.10 and, therefore, the build still fails. It seems to me 
> that base thinks that Clang 5 and above do support this () .So it makes 
> sense that these compilers are used but it doesn’t seem to work. For now 
> I think I’ll just switch the option off for older OS X versions or try 
> to blacklist Clang < 7 and see it that helps.
> 
> Thanks,
> Renee
> 
> 
>> On Nov 20, 2019, at 10:22 PM, Joshua Root <jmr at macports.org 
>> <mailto:jmr at macports.org>> wrote:
>>
>> On 2019-11-21 13:38 , Renee Otten wrote:
>>> dear all,
>>>
>>>
>>> one of the PRs I just merged
>>> (https://github.com/macports/macports-ports/pull/5848) fails on OS X
>>> 10.8, 10.9, and 10.10 with the error "error: thread-local storage is not
>>> supported for the current target” (with AppleClang version 5.1, 6.0, and
>>> 7.0, respectively). On 10.7 it works
>>> again because /opt/local/bin/clang++-mp-9.0 is used as compiler, I
>>> assume because of the "compiler.cxx_standard 2011” statement.
>>>
>>> Looking at other Portfiles there seem to be two approaches to resolve 
>>> this:
>>> 1. if ${os.major} < 11, disable “thread_local” which is doable for the
>>> port in question, but it will then also be disabled on 10.7 where is
>>> seems to work now
>>> 2. blacklists compilers using "compiler.blacklist-append {clang < 700}”
>>>
>>> Is there an opinion (or even consensus) about what is the preferred way
>>> of doing this?
>>
>> You are supposed to be able to set `compiler.thread_local_storage yes`
>> and have it Just Work, but I don't know how accurate base's idea of
>> which compilers versions can be used is.
>>
>> - Josh
>