-
Notifications
You must be signed in to change notification settings - Fork 2k
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: parameter packs not expanded with ‘...’ #119
Comments
Just as a data point, I don't have this problem and my compiler versions are:
Note that my GCC version is much older (since I test it on Ubuntu 20.04), while nvcc is from 11.6. Not sure, if that's relevant. |
I got curious and tried it with gcc-11/g++-11:
It succeeded. There must be something else in that Debian environment that makes it wrong. |
A colleague identified the issue as originating from
|
This has reappeared on ubuntu jammy. Default (Aptitude) gcc is 11.2 and cuda version is 11.6. This is also not fixed with downgrading to gcc-10 The problem is that the aptitude version is cuda toolkit version is 11.5. For me this fixed the issue. I guess the aptitude version should be upgraded! |
Switching to gcc/g++-10 worked for me too. The healthy way to do this is to use update-alternatives and set the default to gcc/++-10 for the build. |
This worked for me as well. Specs original GCC/G++ version == 11.2 did not work. Downgraded to 10 and it worked. |
Why the solution is change gcc not change code? |
@jinfagang Do you have an example of what to change for this to work? |
Apparently, this is a C++ syntax problem that has been around for some time - as instanced in this post dated 2015: How do I tell the system to build instant-ngp with g++-12 and gcc-12 instead of versions 11? |
Using the approach recommended by this fixed my issue. Specs: |
I did what @pullitdown said, but still couldn't get it to compile, so I did:
But it still didn't compile and for some reason
Finally resolved via: (now it just finally seemed to compile... but proceed with caution when doing |
Drawing inspirations from @edavalosanaya and the referenced issue, and the stackoverflow question about using gcc in pip command,
|
On Ubuntu 22.04, |
Also worked on my specs: Specs: avoiding upgrade cuda to 11.6 saved a lot of time, thanks a lot! |
Using Kaggle with cuda_12.3 and can't downgrade cuda version is there any way? |
I first tried to downgrade my gcc version from 11 to 10. However this did not work. Using the OS: Ubuntu 22.04.5 LTS |
worked for me, thinks. Firtly, I tried rolling back GCC to gcc-10 and using CUDA version 11.5, but that didn't work. Later, I upgraded CUDA to 11.6 through to "sudo sh cuda_11.6.2_510.47.03_linux.run --toolkit --silent --override" , and the system automatically updated 11.5 to 11.6. After that, I added the following environment variables to ~/.bashrc:
then recompiled, and the issue was resolved! ENV: |
Getting this error on Ubuntu jammy with gcc 11 and 12, cuda-toolkit-12-8. |
I suspect this issue is not directly related to instant-ngp's code, but I'll post it here all the same in case anyone else sees a similar issue.
TL;DR there's an issue compiling
std_function.h
, a dependency oftiny-cuda-nn
.Here's a bit more info on my setup. I'm using CUDA v11.4.4 and GCC v.11.2.0 on Debian. I saw an identical issue when compiling with CUDA v11.6.0.
Any tips appreciated!
The text was updated successfully, but these errors were encountered: