-
Notifications
You must be signed in to change notification settings - Fork 88
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
#error: STL1002: Unexpected compiler version, expected CUDA 10.1 Update or newer #61
Comments
Hi @AlanSpencer2, thanks for your feedback. |
I downloaded the branch with the following command but got the same error as before when trying to build it: When it comes to compiler version, I downloaded "Desktop development with C++" only a few days ago for Visual Studio 2019. What compiler version do you require? Please see the following image for detailed info about the error. The last two rows are slightly different than the original error above. |
Hi @AlanSpencer2, it seems that your CUDA library is not configured or installed correctly. Please refer to this link (or other CUDA installation tutorials) and check your system path mentioned in the section 5.3. After correct installation of CUDA 11, |
What makes you think that the problem is caused by CUDA not being correctly installed? I just ran XGBoost in Python, which utilizes CUDA for parallel computation on the GPU. And it worked just fine. In Python I get the following information, that shows that CUDA 11 is correctly installed, and the GPU is accessible and ready to be used. Please see the pircture below. And yes, I did run "git submodule init && git submodule udpate". |
I followed your instructions "How to build the Python wheel file for Windows". When I try to build thundergbm.sln in Visual Studio, I get the following error: "#error: STL1002: Unexpected compiler version, expected CUDA 10.1 Update or newer"
I have CUDA version 11.1. Could this be the cause of thunderGBM not building or is there something else?
Please see the picture below for more detailed information about the error.
The text was updated successfully, but these errors were encountered: