Remove statically linked CUDA runtime check in Java build #10532
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.
#9873 added static linking of the CUDA runtime by default in Java cudf builds from the
build-in-docker.sh
. At the end of the script is a sanity check that the CUDA runtime is not statically linked which should have been removed, but it fails to trigger due to an empty.so
file found during the build that causes an error inreadelf
and prevents the script from exiting early. This PR removes the check since a statically linked CUDA runtime is supported and tested.