-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Fix compatibility with CUDA - Clang - CMake 3.20.0 toolchain #4106
Comments
I have an account and can ask! |
Great! Many thanks! |
@jameslamb Have they already answered anything? |
Sorry, I haven't asked yet. I want to come to them with a smaller reproducible example since LightGBM is a fairly large project. I think that will improve the eventual quality of the answer we get. I have access to a machine with an NVIDIA GPU and cuda 10.2 so I think I can make such a smaller reproducible example. If I can't figure that out in the next day or two I'll just ask about LightGBM directly. |
Ok I've opened an issue with I wasn't able to create a non-LightGBM reproducible example, but I at least cut most of See that link for more information on the reproducible example. Sharing it here too: git clone --recursive --branch cuda-cmake-repro git@github.com:jameslamb/LightGBM.git
cd LightGBM
# this will compile successfully
docker run \
-v $(pwd):/opt/test \
-w /opt/test \
--env DEBIAN_FRONTEND=noninteractive \
-t nvcr.io/nvidia/cuda:11.2.2-devel \
./test-cuda.sh
# this will fail with the error mentioned above
docker run \
-v $(pwd):/opt/test \
-w /opt/test \
--env DEBIAN_FRONTEND=noninteractive \
-t nvcr.io/nvidia/cuda:10.0-devel \
./test-cuda.sh
# this will fail with the error mentioned above
docker run \
-v $(pwd):/opt/test \
-w /opt/test \
--env DEBIAN_FRONTEND=noninteractive \
-t nvcr.io/nvidia/cuda:9.0-devel \
./test-cuda.sh This error does NOT show up in the CUDA 11.2.2 image used in testing.
|
Thank you very much for minimizing the repro and posting the issue! |
Yeah agreed :/ Happy to say the |
Wow, this is just awesome! |
Upstream issue fixed in CMake |
This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Our CUDA+Clang builds are incopatible with very recently released CMake 3.20.0 version:
Found Clang, but using gcc.
Here is how we are supporting non-default compiler (Clang):
https://github.com/microsoft/LightGBM/pull/3886/files#diff-1e7de1ae2d059d21e1dd75d5812d5a34b0222cef273b7c3a2af62eb747f9d20a
LightGBM/.ci/test.sh
Lines 6 to 9 in ab474dc
For now we are restricting CMake versinon:
LightGBM/.ci/setup.sh
Lines 100 to 107 in ab474dc
Does anybody have a GitLab account to ask CMake team what has changed in
3.20.0
version because it looks like a regression problem on CMake side?https://gitlab.kitware.com/cmake/cmake/-/issues
The text was updated successfully, but these errors were encountered: