llvm-trunk will fail building if python-2 is not active. See for example: http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-November/045769.html Reproducible: Always Steps to Reproduce: 1. set python-3 as active version 2. emerge =sys-devel/llvm-9999 3. Actual Results: build fails due to a missing LibraryDependencies.inc which never got generated Expected Results: builds :)
Created attachment 303603 [details, diff] set python-2 in ebuild the patch properly adds commands to set the required python version
Thanks for the heads-up and patch! I will commit it when checking clang-9999 include path problem
Ok, clang will be a bigger problem, I have fixed llvm-9999 in the meantime Thanks for the report and patch!
Thanks. :) About clang. It is also on my todo but with my degree dissertation deadline approaching rapidly, I am very short on time. Basically I wanted to talk with the clang guys about this once more, even though they are not very fond of the Gentoo way with regard to this issue. The toolchain-gcc option does us no real good. And there is no way to fix the gcc version by default anymore except for really patching the code which I would prefer to avoid. I considered a wrapper script and such but that all seems suboptimal, especially since it would involve passing a few options to clang instead of just one. And using gcc-config in such a wrapper is out of the question because it is a quite expensive call imho which would further complicate things. For now, my workaround is to set a symlink in /usr/lib/gcc-lib/{arch}/ to the current version with a high enough version number, something link 99.99.99-clang-default -> 4.6.2. This is a bad hack (and could be implemented in a eselect config) but it works with their detection magic. :( Once I have some news about this by myself, I will update the other bug... where I should have put this in the first place. Well. :)
