Package Details: cuda-12.5 12.5.0-3

Git Clone URL: https://aur.archlinux.org/cuda-12.5.git (read-only, click to copy)
Package Base: cuda-12.5
Description: NVIDIA's GPU programming toolkit
Upstream URL: https://developer.nvidia.com/cuda-zone
Licenses: custom:NVIDIA
Conflicts: cuda, cudnn
Provides: cuda, cuda-sdk, cuda-toolkit
Replaces: cuda-sdk, cuda-toolkit
Submitter: SDuesterhaupt
Maintainer: SDuesterhaupt
Last Packager: SDuesterhaupt
Votes: 1
Popularity: 0.013059
First Submitted: 2025-09-03 10:28 (UTC)
Last Updated: 2025-09-03 10:28 (UTC)

Dependencies (6)

Required by (491)

Sources (32)

Latest Comments

SDuesterhaupt commented on 2026-03-08 14:46 (UTC) (edited on 2026-03-08 15:15 (UTC) by SDuesterhaupt)

@fnordinger

Thanks a lot for the details and for offering to help debug this!

To make sure we are looking at the same thing, could you please try building the package once via the “classic” AUR workflow (without yay etc.) and send me the exact steps you are running? For example, something like:

  1. git clone https://aur.archlinux.org/cuda-12.5.git
  2. cd cuda-12.5
  3. git diff
  4. makepkg -g
  5. makepkg -s

If your actual commands differ, please paste your full “recipe” so I can reproduce your setup as closely as possible.

In addition, I’m very interested in the sha512sum binary on your system. Could you please send me:

  • The version of sha512sum, e.g. the output of
    sha512sum --version
  • The checksum of that binary itself, e.g.
    sha512sum "$(command -v sha512sum)"

Please include the full outputs of these commands in your reply. That should help narrow down whether this is an environment-specific issue or something in the PKGBUILD that I’m not seeing on my side.

Thanks again for your support!

fnordinger commented on 2026-03-06 14:19 (UTC)

Hello, just wanted to chime in and say that I have had the same issue as omnigenous (with the same packages). Cloning the repository didn't work for me either. I solved it by changing all the checksums in /.cache/yay/cuda-12.5/PKGBUILD to 'SKIP'. Since I had the issue with the same packages as omnigenous, I guess those checksums are just outdated and have to be renewed. Till then the workaround is not too difficult.

@Sduesterhaupt: If you still need somebody to reach out to you with regards to the problem let me know. Happy to help, if the issue is not replicable on all machines.

SDuesterhaupt commented on 2025-09-25 18:57 (UTC) (edited on 2025-09-25 22:58 (UTC) by SDuesterhaupt)

Well, I have set up a current minimal Arch Linux system. Package creation, as described, works for me like a charme. The checksum verification didn’t reveal any issues.

I have created a screenshot. If you have an XMPP/Jabber or email address, I can send it to you. Please contact me privately.

omnigenous commented on 2025-09-25 13:36 (UTC) (edited on 2025-09-25 14:06 (UTC) by omnigenous)

Arch Linux, I didn't modify PKGBUILD manually. Also using yay with all updates installed.

SDuesterhaupt commented on 2025-09-25 12:13 (UTC) (edited on 2025-09-25 12:13 (UTC) by SDuesterhaupt)

Then let’s take a step back.

I’m using Manjaro with all current updates and yay as my AUR helper.

What about you?

The fact that the checksum verification fails can have the following causes:

  • Files are modified immediately after download

  • In the PKGBUILD, the checksums of the affected files are manipulated

omnigenous commented on 2025-09-25 12:05 (UTC)

Weird, same exact validity check errors. I wonder what I'm missing here.

SDuesterhaupt commented on 2025-09-25 10:11 (UTC) (edited on 2025-09-25 10:11 (UTC) by SDuesterhaupt)

I have checked the following:

Backup the current package repo:

cd ~/.cache/yay
mv cuda-12.5 cuda-12.5.bak-250925

Clone the cuda-12.5 package base:

git clone https://aur.archlinux.org/cuda-12.5.git
cd ~/.cache/yay/cuda-12.5

Build the package:

makepkg -s

In my case, the checksum verification passes without errors.

If further problems occur, the contents of the affected files between the GIT repo and the local repo would need to be compared.

SDuesterhaupt commented on 2025-09-25 09:57 (UTC) (edited on 2025-09-25 09:58 (UTC) by SDuesterhaupt)

In the meantime, you can manually check the routine:

cd ~/.cache/yay/cuda-12.5
makepkg -s

This will create the package without installation. Please check the output.

SDuesterhaupt commented on 2025-09-25 09:51 (UTC)

I am on it...

omnigenous commented on 2025-09-25 09:36 (UTC)

Can't isntall

==> Validating source files with sha512sums...
    cuda_12.5.0_555.42.02_linux.run ... Passed
    cuda.sh ... Passed
    cuda.conf ... Passed
    cuda-findgllib_mk.diff ... Passed
    accinj64.pc ... Passed
    cublas.pc ... Passed
    cuda.pc ... Passed
    cudart.pc ... Passed
    cufft.pc ... Passed
    cufftw.pc ... Passed
    cuinj64.pc ... Passed
    curand.pc ... Passed
    cusolver.pc ... Passed
    cusparse.pc ... Passed
    nppc.pc ... Passed
    nppi.pc ... FAILED
    nppial.pc ... FAILED
    nppicc.pc ... FAILED
    nppicom.pc ... FAILED
    nppidei.pc ... FAILED
    nppif.pc ... FAILED
    nppig.pc ... FAILED
    nppim.pc ... FAILED
    nppist.pc ... Passed
    nppisu.pc ... Passed
    nppitc.pc ... Passed
    npps.pc ... Passed
    nvToolsExt.pc ... FAILED
    nvgraph.pc ... FAILED
    nvidia-ml.pc ... FAILED
    nvjpeg.pc ... FAILED
    nvrtc.pc ... FAILED
==> ERROR: One or more files did not pass the validity check!