Closed kajc10 closed 2 years ago
Do you maybe have multiple CUDA SDK installations on your system?
Can you print what you see when you run:
nvcc -v
I would check the build env variables and perhaps set something like this explicitly to rule it out:
export CUDA_HOME=/usr/local/cuda
export PATH="/usr/local/cuda/bin:$PATH"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/cuda/lib64"
export LIBRARY_PATH="$LIBRARY_PATH:/usr/local/cuda/lib64"
What may be happening here is that CMAKE may be finding an old CUDA SDK on your system and can not link some of the symbols from newer CUDA versions.
Yes, I did have some problems with CUDA.
(I'm working on a remote container and at every reset my env variables were lost -> nvcc -V showed CUDA 9.1 instead of 11.6.
To solve it I only wrote the following lines to .bash-profile)
export PATH=/usr/local/cuda-11.6/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/usr/local/cuda-11.6/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
Now issuing your snippet, the build completes, thanks.
Build fails on headless container, any ideas what could be the problem? Specs: Ubuntu 18.04.6 LTS CUDA 11.6 Tesla V100 (DGX station 4pcs) Python 3.9.7 cmake 3.22.3 gcc/g++ 7.5.0
root@610d9320bd51:~/workdir/instant-ngp# cmake . -B build -DNGP_BUILD_WITH_GUI=off
root@610d9320bd51:~/workdir/instant-ngp# cmake --build build --config RelWithDebInfo -j 16
...long output... end of output:The full output is too long, I attach it as a link: error.txt