-
-
Notifications
You must be signed in to change notification settings - Fork 3
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 #9
Rebuild for CUDA 12 #9
Conversation
…nda-forge-pinning 2023.06.01.08.10.30
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 ( |
Seeing the following error on CI:
As the new CUDA 12 packages split all these components up ( conda-forge/staged-recipes#21382 ), think we need to add host:
- libcufft-dev # [(cuda_compiler_version or "").startswith("12")] Note that Edit: For more info about the CUDA 12 bringup, please see issue ( conda-forge/conda-forge.github.io#1963 ) |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.06.27.08.33.03
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
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 ( |
Attempted to resolve the conflicts with the merge commit above |
Thanks, that worked, it's unfortunately back to the same issue. I believe this is a nvcc bug on some "creative" syntax used in pybind11, see pybind/pybind11#4606 . Appears that the nvcc team has an internal bug for this issue and it should be fixed in a future release. I don't think it makes sense for us to try to patch this, we can just wait for upstream fixes. |
The combination of pybind11 + GCC 12 + nvcc 12 runs into compilation errors. This is documented in a pybind11 issue. To workaround this, configure the CUDA 12 migrator to use GCC 11, which shouldn't have this issue. xref: pybind/pybind11#4606
…nda-forge-pinning 2023.06.27.16.55.53
Yeah noticed that issue recently Have had some success using GCC 11 instead ( conda-forge/pp-sketchlib-feedstock#40 ) Tried pushing similar changes here |
Looks like that got past the compilation issue and the build completed 🎉 Now seeing this failure in the test phase on CI import: 'CyRSoXS'
Traceback (most recent call last):
File "/home/conda/feedstock_root/build_artifacts/cyrsoxs_1687903533456/test_tmp/run_test.py", line 2, in <module>
import CyRSoXS
ImportError: libnppig.so.12: ELF load command address/offset not properly aligned Looks like the libraries in |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.08.08.11.45.19
Due to the |
Superseded by PR: #12 |
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/5144410809, please use this URL for debugging.