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
- Re: OSX 10.6 clang / llvm circular dependency Jeremy Lavergne
- Re: OSX 10.6 clang / llvm circular dependency Michael Dickens
- Re: OSX 10.6 clang / llvm circular dependency Chris Jones
- Re: OSX 10.6 clang / llvm circular dependen... Eric A. Borisch
- Re: OSX 10.6 clang / llvm circular depe... Michael Dickens
- Re: OSX 10.6 clang / llvm circular... Christopher Jones
- Re: OSX 10.6 clang / llvm circ... Michael Dickens
- Re: OSX 10.6 clang / llvm circ... Michael Dickens
- Re: OSX 10.6 clang / llvm circ... Chris Jones
- Re: OSX 10.6 clang / llvm circ... Michael Dickens
- Re: OSX 10.6 clang / llvm circ... Michael Dickens
- Re: OSX 10.6 clang / llvm circ... Christopher Jones
- Re: OSX 10.6 clang / llvm circ... Joshua Root
- Re: OSX 10.6 clang / llvm circ... Chris Jones
- Re: OSX 10.6 clang / llvm circ... Michael Dickens
- Re: OSX 10.6 clang / llvm circular dependency Ken Cunningham
- Re: OSX 10.6 clang / llvm circular dependency Michael Dickens
- Re: OSX 10.6 clang / llvm circular dependency Ken Cunningham
- Re: OSX 10.6 clang / llvm circular dependency Michael Dickens
