-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cudaPackages.cudatoolkit: switch to autoPatchelf #178440
Conversation
3bdbc07
to
08e6a91
Compare
08e6a91
to
b08df4e
Compare
These two are just hanging around. I'm almost certain I should remove |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a great upgrade to cudaPackages.cudatoolkit! I'm running nixpkgs-review now...
Result of 2 packages marked as broken and skipped:
5 packages failed to build:
33 packages built:
|
Here are the errors:
Looks like cudatoolkit 10.1 and 10.2 are broken. Not sure if we're still trying to keep those working? I assume a number of packages still rely on them though. |
OTOH the failures are only in the |
...to ensure correctness (in the sense that all DT_NEEDED libraries are verified to be discoverable through the runpaths)
...the same logic is handled by autoPatchelf
b08df4e
to
15848ff
Compare
I re-based on current ❯ nix-build with-my-cuda.nix -A cudaPackages_10.cudatoolkit.out -A cudaPackages_10_1.cudatoolkit.lib -A cudaPackages.cudatoolkit
/nix/store/80q92g4mw49cifxfzhk3xhfmhcq7635p-cudatoolkit-10.2.89
/nix/store/vfkbm851wjfpw1pc2mdxq5v7d49plkps-cudatoolkit-10.1.243-lib
/nix/store/chzf3k3s07wd9i7xgzg6ha667bjhpc51-cudatoolkit-11.7.0 ...nixpkgs-review would be nice, but I probably can't run it any time soon |
I think it would be pragmatic to just merge, relying on autoPatchelf having verified all the declared dependencies. There may be hidden |
Dobriy den' @SomeoneSerge. I've recently updated nixpkgs channel confugration and xmrig-cuda library that depends on cuda - just stopped working with this error: I fixed it by downgrading nixpkgs to Any ideas how it could be related to this changes? How to fix? |
@MrFoxPro Hey-hey, и Вам доброго дня! First off, I see that you're linking to As for the libnvrtc error and whether it's not being found or being rejected by the dynamic linker, we'll need to see more logs. I'd start with running xmrig with I also see that there is an |
@MrFoxPro On a side note, though... I don't know what you mean by the "PMC Balloon", but to me it sounds a little bit provoking, and not in a good way. This is going off-topic though |
I'm not sure about |
just a meme :) you're welcome to join https://t.me/ru_nixos btw, so we can discuss it more closely if you want |
The name But let's draft a PR and move the conversation there!
Alright, alright, I didn't mean to imply anything. Just that there are times when waving a white flag high above your head before approaching people is suddenly a very common sense thing to do, lest you catch friendly fire |
@SomeoneSerge lets discuss it #224848 |
Description of changes
Rewrites
cudatoolkit
expression to useautoPatchelf
instead of manually constructing and writing therpath
.Using
autoPatchelf
ensures that we're at least not missing dependencies that upstream has marked as "needed".This is a narrow-scoped part of #178439
For instance, this PR ensures "correctness" (amend missing rpaths) but increases the actual closure size.
The next PR should split the output to reduce closure sizes, while preserving "correctness"
Things done
CC @NixOS/cuda-maintainers