OSX 10.6 clang / llvm circular dependency

Joshua Root jmr at macports.org
Fri Feb 8 22:19:35 UTC 2019

On 2019-2-9 08:39 , Christopher Jones wrote:
>> On 8 Feb 2019, at 9:32 pm, Michael Dickens <michaelld at macports.org
>> <mailto:michaelld at macports.org>> wrote:
>> Adding in some debug printouts inside portconfigure.tcl, I think
>> what's happening is that when "libc++" is specified, somewhere
>> inside portconfigure.tcl the possible compilers to used gets pared
>> down. Since I'm not specifying one by default, and there is no
>> blacklist or whitelist, the fallback list is used. The first
>> "compiler.fallback" on OSX 10.6 that meets the requirement to support
>> "libc++" is "macports-clang-7.0". Not sure if this help anyone, but it
>> explains why the dependency on clang-7.0 for cmake at least. - MLD
> OK, but why then do you see this on OSX 10.6, but I don’t (i.e. see my
> first mail, with the clang/llvm deps) ?
> Something has to be different between the two, to get a different outcome.

Current release of base vs master perhaps?

- Josh

More information about the macports-dev mailing list