OSX 10.6 clang / llvm circular dependency

Christopher Jones jonesc at hep.phy.cam.ac.uk
Fri Feb 8 21:39:34 UTC 2019

> On 8 Feb 2019, at 9:32 pm, Michael Dickens <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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20190208/8f38c671/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1930 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20190208/8f38c671/attachment.bin>

More information about the macports-dev mailing list