| View previous topic :: View next topic |
| Author |
Message |
iandoug
l33t
Joined: 11 Feb 2005
Posts: 860
Location: Cape Town, South Africa
|
 Posted: Sun Apr 13, 2025 7:39 am Post subject: Problem emerging nvidia-cuda-toolkit [Solved] |
 |
|
Hi
Had this problem for a while, thought it may auto-resolve but does not.
Is it Python-related, or something else?
| Code: |
>>> Emerging (1 of 1) dev-util/nvidia-cuda-toolkit-12.8.1::gentoo
* cuda_12.8.1_570.124.06_linux.run BLAKE2B SHA512 size ;-) ... [ ok ]
* Checking for at least 6608 MiB disk space at "/var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/temp" ... [ ok ]
* Checking whether python3_13 is suitable ...
* dev-lang/python:3.13 ... [ ok ]
* python_check_deps ...
* dev-python/defusedxml[python_targets_python3_13(-)] ... [ !! ]
* Checking whether python3_12 is suitable ...
* dev-lang/python:3.12 ... [ ok ]
* python_check_deps ...
* dev-python/defusedxml[python_targets_python3_12(-)] ... [ !! ]
* Checking whether python3_11 is suitable ...
* dev-lang/python:3.11 ... [ ok ]
* python_check_deps ...
* dev-python/defusedxml[python_targets_python3_11(-)] ... [ ok ]
* Using python3.11 in global scope
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/work
>>> Preparing source in /var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/work ...
* Applying nvidia-cuda-toolkit-glibc-2.41-r1.patch ... [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/work ...
>>> Source compiled.
* Skipping make test/check due to ebuild restriction.
>>> Test phase [disabled because of RESTRICT=test]: dev-util/nvidia-cuda-toolkit-12.8.1
>>> Install dev-util/nvidia-cuda-toolkit-12.8.1 into /var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/image
* parsing manifest /var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/work/manifests/cuda_x86_64.xml ...
* ERROR: dev-util/nvidia-cuda-toolkit-12.8.1::gentoo failed (install phase):
* failed to parse manifest
*
* Call stack:
* ebuild.sh, line 136: Called src_install
* environment, line 2004: Called die
* The specific snippet of code:
* "${EPYTHON}" "${FILESDIR}/parse_manifest.py" "${S}/manifests/cuda_"*".xml" &> "${T}/install.sh" || die "failed to parse manifest";
*
* If you need support, post the output of `emerge --info '=dev-util/nvidia-cuda-toolkit-12.8.1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-util/nvidia-cuda-toolkit-12.8.1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/work'
* S: '/var/tmp/portage/dev-util/nvidia-cuda-toolkit-12.8.1/work'
>>> Failed to emerge dev-util/nvidia-cuda-toolkit-12.8.1, Log file:
|
Thanks, Ian
_________________
Asus X570-PRO, Ryzen 7 5800X, GeForce GTX 1650, 32 GB RAM | Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram
Last edited by iandoug on Sun Apr 13, 2025 3:01 pm; edited 1 time in total |
|
| Back to top |
|
 |
bstaletic
Guru
Joined: 05 Apr 2014
Posts: 493
|
|
| Back to top |
|
|
iandoug
l33t
Joined: 11 Feb 2005
Posts: 860
Location: Cape Town, South Africa
|
| Posted: Sun Apr 13, 2025 3:01 pm Post subject: |
|
|
Thanks, discovered I had specified python version in make.conf some time back because a package demanded it.
Removed that, 372 installs later, all is done.
Thanks, Ian
_________________
Asus X570-PRO, Ryzen 7 5800X, GeForce GTX 1650, 32 GB RAM | Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2934
|
| Posted: Sun Apr 13, 2025 3:22 pm Post subject: |
|
|
| iandoug wrote: | | Thanks, discovered I had specified python version in make.conf some time back because a package demanded it. |
It is discouraged to use make.conf for that precisely because of such issues. Use package.use instead. Also afair things in make.conf can override some of your profile settings.
Best Regards,
Georgi |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
