The ebuild inherits cuda even when USE=-cuda. When there is a cuda-config in $PATH, that fails with: >>> Preparing source in /var/tmp/portage/dev-util/VampirTrace-5.14.3/work/VampirTrace-5.14.3 ... * ERROR: dev-util/VampirTrace-5.14.3 failed (prepare phase): * Could not determine supported gcc versions from cuda-config When there is not, it fails with: >>> Preparing source in /var/tmp/portage/dev-util/VampirTrace-5.14.3/work/VampirTrace-5.14.3 ... /var/tmp/portage/dev-util/VampirTrace-5.14.3/temp/environment: line 636: cuda-config: command not found * Could not execute cuda-config * Make sure >=dev-util/nvidia-cuda-toolkit-4.2.9-r1 is installed * ERROR: dev-util/VampirTrace-5.14.3 failed (prepare phase): * cuda-config not found Given that the ebuild only depends on dev-util/nvidia-cuda-toolkit when USE=cuda, and cuda.eclass obviously requires dev-util/nvidia-cuda-toolkit, the ebuild only should inheric cuda when USE=cuda. (Or cuda.eclass should be fixed to be idenpotent when dev-util/nvidia-cuda-toolkit is not installed.)
James- thanks for reporting this bug. I hadn't caught it as all my boxes have the CUDA toolkit installed. I was able to reproduce the bug after unmerging it. Fixed in https://github.com/gentoo-science/sci/pull/67/files Best -Andreas
