On Monday December 22 2014 12:43:46 Lawrence Velázquez wrote: > > Well, invoking /usr/bin/clang directly will of course use the CLT version. > > No. As I said, invoking /usr/bin/clang invokes the compiler in your active > tools directory.
We're saying the same thing (except that my statement was missing a "if the CLT are the active tool chain"). > (I think. It could hypothetically use the compiler selected by `xcrun`, but > I've never butchered `xcrun` to do the wrong thing.) Actually, it's doing the right thing. The xc in xcrun stand for Xcode, not for Command Line Utilities, so it could be argued that my wrapper in fact corrects an erratic behaviour. O:-) If no one is interested in getting clang to build without using Xcode, fine, I'll just clean the port and wait until v 3.6 hits release quality/status. Hopefully I'll have been able to update my Xcode too by then. R _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
