Created attachment 494070 [details] build logs concatenated with `tail -n +1` I suspect its a dependency issue, or portage's resolver (specifically, I know fun things can happen around --onlydeps, but this doesn't really look like how that typically pans out) FEATURES=-test emerge -t1 --quiet-build=y --quiet-repo-display --nospinner --autounmask=y --autounmask-keep-masks=y --autounmask-unrestricted-atoms=n --autounmask-unrestricted-atoms=n --autounmask-continue --unordered-display --verbose --backtrack=10 --onlydeps --with-test-deps=y =sys-devel/clang-5.0.0 ... [nomerge ] sys-devel/clang-5.0.0:5 [3.8.1-r100:0/3.8] USE="doc static-analyzer -debug -default-compiler-rt -default-libcxx {-test} -xml (-z3)" LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARM -BPF -Hexagon -Lanai -MSP430 -Mips -NVPTX -PowerPC -Sparc -SystemZ -XCore" PYTHON_TARGETS="python2_7" [ebuild N ~] sys-devel/clang-runtime-5.0.0:5.0.0 USE="compiler-rt openmp sanitize -libcxx" 0 KiB [ebuild N ~] sys-libs/compiler-rt-5.0.0:5.0.0 USE="clang {-test}" 1,473 KiB [ebuild N ~] sys-libs/compiler-rt-sanitizers-5.0.0:5.0.0 USE="{-test}" 0 KiB [ebuild U ~] sys-libs/libomp-5.0.0:0/0 [3.9.0:0/3.9] USE="-hwloc -ompt {-test%}" 2,026 KiB ... >>> Working in BUILD_DIR: "/var/tmp/portage/sys-libs/compiler-rt-5.0.0/work/compiler-rt-5.0.0_build" cmake -C /var/tmp/portage/sys-libs/compiler-rt-5.0.0/work/compiler-rt-5.0.0_build/gentoo_common_config.cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/usr -DCOMPILER_RT_INSTALL_PATH=/usr/lib/clang/5.0.0 -DCOMPILER_RT_INCLUDE_TESTS=no -DCOMPILER_RT_BUILD_SANITIZERS=OFF -DCOMPILER_RT_BUILD_XRAY=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_USER_MAKE_RULES_OVERRIDE=/var/tmp/portage/sys-libs/compiler-rt-5.0.0/work/compiler-rt-5.0.0_build/gentoo_rules.cmake -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/sys-libs/compiler-rt-5.0.0/work/compiler-rt-5.0.0_build/gentoo_toolchain.cmake /var/tmp/portage/sys-libs/compiler-rt-5.0.0/work/compiler-rt-5.0.0.src loading initial cache file /var/tmp/portage/sys-libs/compiler-rt-5.0.0/work/compiler-rt-5.0.0_build/gentoo_common_config.cmake -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- The ASM compiler identification is unknown -- Found assembler: x86_64-pc-linux-gnu-clang CMake Error at CMakeLists.txt:14 (project): The CMAKE_C_COMPILER: x86_64-pc-linux-gnu-clang is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. CMake Error at CMakeLists.txt:14 (project): The CMAKE_CXX_COMPILER: x86_64-pc-linux-gnu-clang++ is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. CMake Error at CMakeLists.txt:14 (project): The CMAKE_ASM_COMPILER: x86_64-pc-linux-gnu-clang is not a full path and was not found in the PATH. Tell CMake where to find the compiler by setting either the environment variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. -- Warning: Did not find file Compiler/-ASM -- Configuring incomplete, errors occurred!
Specifying the correct package helps me save time not trying to figure out wtf did you get USE=clang from.
PEBKAC. This is a circular dependency (clang PDEP runtime RDEP compiler-rt DEP clang), and your --onlydeps hackery attempts to satisfy it in the wrong order.
(In reply to Michał Górny from comment #2) > and your --onlydeps hackery attempts to satisfy it in the wrong > order. I'd probably say then this makes it a portage bug among the handful of other --onlydeps bugs. But its understandably a mess trying to do the right thing here.
