x11 would like to have sys-devel/llvm-3.4.2 stabilized as it is needed for >=dev-libs/libclc-0.0.1_pre20140101
Maintainers: If you agree please, CC arches.
I think it's safe to go. However, I would consider doing 3.5.0 instead if that's good for you as well. I don't think our revdeps really care -- they either support newest llvm, or require an ancient one ;).
Yes, 3.5.0 is fine too. I wasn't sure whether 3.5.0 is ready for stable due to bug 522318.
3.5.0 looks good to me too, and libclc-0.0.1_pre20140101-r1 includes a patch to make it work
Arches, please test and mark stable =sys-devel/llvm-3.5.0, thanks!
sys-devel/llvm/llvm-3.5.0.ebuild: PDEPEND: amd64(default/linux/amd64/13.0) ['=sys-devel/clang-3.5.0-r100']
I am failing to merge it on ppc64:
# emerge -1 =sys-devel/llvm-3.5.0 =sys-devel/clang-3.5.0-r100 --jobs=4
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy "~sys-devel/llvm-3.5.0[clang(-),debug=,multitarget?,python?,static-analyzer,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]".
(dependency required by "sys-devel/clang-3.5.0-r100" [ebuild])
(dependency required by "=sys-devel/clang-3.5.0-r100" [argument])
OK, looks like the clang USE-flag is not masked in ppc64/32ul (or globally in ppc64), it is only masked in 64ul and clang itself is not keyworded on ppc64.
But I'd rather have confirmation from someone on the team ;) Can you check and fix if needed the masks for your arch? After that stabilization can go on for =sys-devel/llvm-3.5.0 only
Btw, clang 3.5/3.6 should work fine on ppc64 and could use a keyword request/try, but this can be done much later at your convenience (and interest)
ppc64 stable. Closing.