-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Rebuild for CUDA 12 w/arch + Windows support #56
Rebuild for CUDA 12 w/arch + Windows support #56
Conversation
The transition to CUDA 12 SDK includes new packages for all CUDA libraries and build tools. Notably, the cudatoolkit package no longer exists, and packages should depend directly on the specific CUDA libraries (libcublas, libcusolver, etc) as needed. For an in-depth overview of the changes and to report problems [see this issue]( conda-forge/conda-forge.github.io#1963 ). Please feel free to raise any issues encountered there. Thank you! 🙏
…nda-forge-pinning 2023.11.16.09.46.51
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Some aarch64/ppc64le cuda builds are failing with:
Probably it is just an out of memory issue? |
@conda-forge-admin re-render |
…nda-forge-pinning 2023.11.16.09.46.51
The file that is failing is a simple file used by CMake to identify the CUDA compiler use, so I think it is not an out of memory issue. |
@conda-forge-admin , please re-render |
…nda-forge-pinning 2023.12.01.08.31.55
@conda-forge-admin , please re-render |
…nda-forge-pinning 2023.12.01.08.31.55
@conda-forge-admin , please re-render |
…nda-forge-pinning 2023.12.01.08.31.55
Cleaned up disk space on Azure and switched to cross-compilation, which appears to have addressed the memory issue |
Seeing these errors from CMake on CI
Maybe this logic needs to be reworked a bit librealsense-feedstock/recipe/build.sh Lines 26 to 29 in 45ef8a2
|
Thanks @jakirkham ! Yes now that only 11.8 + 12 are supported we can simplify that code (I can work on this in a few days), thanks for chiming in. |
@conda-forge-admin , please re-render |
1 similar comment
@conda-forge-admin , please re-render |
@conda-forge-admin , please re-render |
…nda-forge-pinning 2024.03.07.00.29.48
Would add requirements:
...
host:
...
- cuda-version {{ cuda_compiler_version }} # [(cuda_compiler_version or "None") != "None"] This will ensure that |
@conda-forge-admin , please re-render |
…nda-forge-pinning 2024.03.07.13.21.27
Travis build of ppc64 are super-slow. I think it make sense to disable CUDA for ppc64, and switch back ppc64 to use cross-compilation (where CUDA was failing). |
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.
Thanks Silvio! 🙏
Added a few suggestions to see if we can get cross-compilation to work
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was not passing and not merged. |
Co-authored-by: jakirkham <jakirkham@gmail.com>
@conda-forge-admin , please re-render |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
Thanks! I just applied them, let's see if they work. |
…nda-forge-pinning 2024.03.07.20.43.08
@@ -44,6 +44,7 @@ requirements: | |||
- python | |||
- libudev # [linux and cdt_name!='cos6'] | |||
- libusb | |||
- cuda-version {{ cuda_compiler_version }} # [(cuda_compiler_version or "None") != "None"] |
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.
It looks like CMake can't find cudart
. So let's add it as a dependency and see if that helps
We should double check whether it is linking to cudart
or not. If not, we may want to add this to ignore_run_exports_from
above
- cuda-version {{ cuda_compiler_version }} # [(cuda_compiler_version or "None") != "None"] | |
- cuda-version {{ cuda_compiler_version }} # [(cuda_compiler_version or "None") != "None"] | |
- cuda-cudart-dev # [(cuda_compiler_version or "None") != "None"] |
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.
Ah, I missed this comment and added it like this dc6ed15 (I added it only for cuda==12 builds).
@conda-forge-admin , please re-render |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/librealsense-feedstock/actions/runs/8196232282. |
Ok think I understand what is happening
Think we can disable CUDA 12 on |
Can't we use the non-crosscompile build, at least aarch64 ? I do not care a lot for ppc64le, but we use a lot this library on Jetson boards, and having CUDA 12 builds but not for aarch64 may be confusing for users from my organization. |
Yeah wasn't sure what level of effort we were going for. So just proposed the simplest approach Certainly we could do native builds if that is tenable for you Another option might be to patch the CMake files to enable cross-compilation here. @Tobias-Fischer did this for |
@conda-forge-admin , please re-render |
…nda-forge-pinning 2024.03.08.18.51.49
This PR has been triggered in an effort to update cuda120.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
Here are some more details about this specific migrator:
If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6899793194, please use this URL for debugging.