dev-util/nvidia-cuda-toolkit: call cuda-config with absolute path

When doing a clean install, cuda-config is not in $PATH yet so the
gcc version check fails with 0.0. Calling with the absolute path fixes
it.

Signed-off-by: Jason Zaman <perfinion@gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11

diff --git a/dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-10.1.105.ebuild b/dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-10.1.105.ebuild
index 0ba04a3b7cc2d12d62e81445c8d3c54ca77368a8..7030ff9fe1de04f043f062966dd2b34d9d76d510 100644 (file)
--- a/dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-10.1.105.ebuild
+++ b/dev-util/nvidia-cuda-toolkit/nvidia-cuda-toolkit-10.1.105.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Authors
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
@@ -115,7 +115,7 @@ src_install() {
 
 pkg_postinst_check() {
        local a b
-       a="$(cuda-config -s)"
+       a="$(${EROOT%/}/opt/cuda/bin/cuda-config -s)"
        b="0.0"
        for v in $a; do
                if ver_test "${v}" -gt "${b}"; then