On Dec 20, 2014, at 12:03 PM, René J.V. Bertin wrote: > I noticed I still had llvm-3.4 installed, and saw that is cctools and ld64 > depend on it. I also noticed llvm-3.6 is now available in MacPorts, so I > decided to replace llvm-3.4 with 3.6, and install clang-3.6 . After all, now > that Apple provides clang-3.5 and my Linux rigs have upgraded to clang-3.5 > too, there's little use to keep an older version, but more in having a newer > version. > > So I (force) uninstalled cctools, ld64 and llvm-3.4, and because clang lists > cctools, ld64 and llvm-3.6 as dependencies I just did a > > #> port install clang-3.6 > > After upgrading a number of dependencies, I got this: > > ---> Computing dependencies for clang-3.6 > ---> Dependencies to be installed: cctools llvm-3.5 ld64 llvm-3.6 > ---> Fetching archive for llvm-3.5 > ---> Attempting to fetch llvm-3.5-3.5.0_1.darwin_13.x86_64.tbz2 from > http://lil.fr.packages.macports.org/llvm-3.5 > ---> Attempting to fetch llvm-3.5-3.5.0_1.darwin_13.x86_64.tbz2.rmd160 from > http://lil.fr.packages.macports.org/llvm-3.5 > ---> Installing llvm-3.5 @3.5.0_1 > > > I think llvm-3.5 is being pulled in because off cctool's and/or ld64's > default variant. Supposing there's no actual need for llvm-3.5, that's not > very nice if you know how large that port is. > Is this a case of sloppy Portfile programming, or a result of the fact ports > can't depend on variants? > > NB: `port info cctools +llvm36 ld64 +llvm36` does not declare a dependency on > llvm-3.5, so that at least appears to be correct.
This is behaving as intended. cctools and ld64 default to llvm-3.5 on Mavericks and later, because that is the latest stable version of llvm. I expect this will be changed to llvm-3.6 when llvm-3.6 becomes the latest stable version. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
