Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
ARM is not compatible with GLIBC 2.17
So think we should stick to GLIBC 2.28 here
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.
Good call. We can equivalently just erase this and let it use the matrix entry below.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.
Agree that looks cleaner. Let's do it 👍
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.
Oops: this is not correct. https://anaconda.org/conda-forge/nvcc_linux-aarch64/files?version=11.4
The aarch64 packages for nvcc 11.4 (up to 11.7) require sysroot 2.17. The current state of the PR (using sysroot 2.17) is correct for all nvcc versions < 11.8, and is the same on x86 and ARM.
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.
I agree that CUDA libraries require glibc versions newer than 2.17 -- but the
nvcc
compiler metapackage for CUDA 11 is only installable withsysroot 2.17
until we get to recent builds ofnvcc 11.8
that permit newer sysroots.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.
@jakirkham I am going to merge this as-is so that we can unblock nightly CI.
I think there's nothing else we should do here, but if you want to lift the restrictions for old CUDA compilers, a follow-up PR would be welcome.
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.
So I had looked into this recently. Here is what I observed:
sysroot
constraint was flagged as a bugnvcc_linux-aarch64 11.8
cannot be installed withsysroot_linux-aarch64 2.28
conda-forge/nvcc-feedstock#107libgcc-ng
in ignore_run_exports conda-forge/nvcc-feedstock#106Typically that is enough to justify a repodata patch and it makes sense
Additionally noticed that
nvcc_{{ target_platform }}
's pinnings could be handled more systematically, which is now fixedpin_compatible
forcudatoolkit
&sysroot
conda-forge/nvcc-feedstock#115Following this submitted a repodata patch
nvcc
'ssysroot
upper bound conda-forge/conda-forge-repodata-patches-feedstock#950The repodata patch landed before last night's nightly run, which passed in CUDA 11.4 (the affected job)
Note there is a CUDA 12.5 failure in that nightly, but that is due to actual test failures
So AFAICT this issue is already fixed
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.
Wonderful. I apologize, I didn't see those PRs, just the end of the Slack conversation, and thought this might have been the best we could do. I appreciate you taking the extra steps, which now allow us to simplify things.
I filed a follow-up to simplify the
dependencies.yaml
and usesysroot 2.28
everywhere in #749.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.
I'm sorry as well. I meant to update this thread with those details and just hadn't had time to do so. The CUDA 12.8 rollout started very soon after
If you are feeling stuck, please feel free to DM me. Am here to help