-
Notifications
You must be signed in to change notification settings - Fork 157
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
Build error on POP! OS 21.10 #49
Comments
The nvcc compiler finds a warning where there should be none A quick fix for you could be to disable the option which treats warnings as errors. This could be done by removing the line But I'd like to understand the reason... Which version of the CUDA Toolkit are you using? |
I tried the quick fix you suggested and the build continued up to the 98% and failed. Here is the build log. Below is the output of
Thank you very much for your quick response! |
I'm not an expert on such linker problems, but it seems to be the same as in https://githubhot.com/repo/owl-project/owl/issues/144 (last post). A workaround is given there. I've modified the build scripts on the |
Thank you very much for the help! Sadly, it didn't work, the output is the same as the one with the quick fix. Disclaimer: this topic is WAY above my head, so, sorry if I'm playing Captain Obvious. I starter diving into the issue from the error jjd@pop-os:~$ ll /usr/lib/x86_64-linux-gnu/librt.a
-rw-r--r-- 1 root root 8 Feb 24 16:45 /usr/lib/x86_64-linux-gnu/librt.a
jjd@pop-os:~$ cat /usr/lib/x86_64-linux-gnu/librt.a
!<arch> There was an gclib update August last year, and this answer in the Arch subredit points to that update as source of possible problems with the Nvidia linker. Little further in the error message, it points to
Finally, in the So, if those files are empty and cause error maybe the solution is somehow fix those links when generating the Or perhaps is related with this issue? Hope this helps to further understand the issue. |
I don't think that I can really help here :-( The linker error on your system seems to occur in general when compiling a CUDA project via a CMake script... |
I did run into the same build error Debian testing/sid while compiling v3.2.1 (the "unused" warning). After I deleted the unused variable in System information, in case it helps someone:
|
Yes it seems to be the cuda version. I have upgraded from 11.4.3 to 11.5.2 ( System info after update:
|
Thanks, good to know! |
Yes, I did run most of It was already working with the old cuda version (with the workaround). I did not run into the linker issue described by Jay-Jay-D, only the initial build-failure (warning). |
60 tps seems a bit slow. Which graphics card do you use? How fast is it without rendering (can be toggled with ALT+I)? |
GeForce GTX 1660 Ti; without rendering I get ~100 (+/- 5) time steps per second. I have also tested on Windows now (dual-boot): ~70 with UI and 100 (+/-5) without. Could be Gnome doing some extra UI steps, IIRC that's a thing. |
Ok, I see. Rendering seems to consume a lot of time here. You can e.g. reduce the frame rate or resolution in the display settings if you want. |
I installed all the required dependencies and followed the instructions on the Readme, and I had no problem, but it failed in the last step
cmake --build . --config Release -j8
.The error message is
POP! OS is based on Ubuntu Impish, the GPU is a GeForce GTX 1060 6GB with nvidia470 driver.
Please ask any other information you need for better understand the issue.
Thanks in advance.
The text was updated successfully, but these errors were encountered: