lldb-6.0 build failure

[Chris Jones]

On 17/01/18 16:03, David wrote:
> I’m on 10.11.6 and completely up to date.
> 
> The problem is that Apple didn’t add thread local support to their version of clang until after 10.11. So my Xcode won’t compile anything that requires thread local support. This is weird. I would expect that any requirement like that would be part of the macport configuration file, rather than waiting until 20+ minutes of compiles have happened and then searching through the output build log to find the reason the build failed.

Not weird. I guess you are just the first to try (and report) building 
lldb-6.0 on OSX 10.11.

If the default system compiler for that OSX is unable to build this 
port, then that port should blacklist that compiler, such that a 
macports provider compiler is used instead that can build it.

You should submit a trac ticket to report this to the relevant 
maintainer. See

https://www.macports.org/

and "report a bug"

Chris

> 
> 	David
> 
>> On Jan 17, 2018, at 7:35 AM, Chris Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>>
>>
>> What OSX version are you running ? Is your Xcode up to date for that version ?
>>
>>> On 17 Jan 2018, at 12:25 pm, David <david at kdbarto.org> wrote:
>>>
>>> I’m using a version of Apple’s clang that doesn’t support thread local storage (Apple LLVM version 7.0.2 (clang-700.1.81), from 2014). When I tried to install lldb-6.0 it failed because that compiler didn’t support thread local storage.
>>>
>>> Is there a way to force the build for lldb-6.0 to use my installed clang (/opt/local/bin/clang-mp-6.0)? /opt/local/bin/clang points at this version.
>>> My PATH is set to have /opt/local/bin prior to /usr/bin, so it wasn’t a PATH issue.
>>>
>>>    David
>>>
>>
>