-
Notifications
You must be signed in to change notification settings - Fork 146
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
nvcc fatal : Stray '"' character #2
Comments
here is cmake echo so you can see configuration details:
|
I also have this issue on a fresh ubuntu 17.04 install |
Ok... I think I have a workaround.. The issue is due to recent If you install an older cmake (cmake 3.5 for instance), the project compliles without this error. |
Thank you for the response, dcoeurjo! Much appreciated. I am too now having this issue on ubuntu 17.04. Certainly, this can be made to compile under more recent cmake somehow, as many will want to use latest ubuntu as their dev machines. |
actually just got this to compile under stock ubuntu 17.04 install using cmake that it ships with (cmake 3.7.2). The issue is that nvidia developers are putting quotes in their paths in the cmake files to help with paths that contain spacing. However, my paths don't have any spacing and their workaround is causing me trouble. nvidia needs a better workaround. |
to compile have to go into source/gvdb_library/cmake/CMakeLists_include.txt and remove quotes from lines 11, 12, 114, 115, 116. |
I got a similar error as above:
I downloaded cmake switched to the branch linked above that should fix the issue, build it without errors, then replaced ccmake, cmake, cpack and ctest with the newly build binaries and tried to build anew with the patch, but I still get the same error, any ideas why this could be? |
I'm facing sane probkem ,How to solve the problem and how to use the mentioned patch ? |
Hi q8wwe! We changed the build system a lot since this issue was originally created, so some things might have changed in the meantime. Could you let me know what version of CMake you're using (and which version of Linux), as well as the command line that nvcc's failing on, if possible? Thanks! |
Ubuntu 16.04 Thank very much for reply back , I tried to solve this problem but no luck . What can I do to overcome this problem and I have no idea how to use the mentioned patch !!! |
OK, the version of CMake's probably the issue here! The minimum version of CMake for the new GVDB build system is 3.10 - see https://github.com/NVIDIA/gvdb-voxels/blob/master/CMakeLists.txt#L4 (this was determined based off of trying to balance the new CMake features we wanted to use to simplify the build system with the fact that Ubuntu 18.04 LTS only has CMake 3.10, if I recall correctly). If possible, maybe the simplest way to apply the patch above (essentially) would be to update to a more recent version of CMake (3.10 or higher)? That should hopefully help with the issue, since it looks like the patch above was committed into the CMake code base about two years ago. Thanks! |
Thank you I will try this solution tomorrow. |
Thank you for your suggestion. Steps :- |
Awesome, I'm glad that worked - and thanks for posting the instructions showing how to install it here! |
On arch linux 4.11.3-1 using cmake 3.8.2, I get the following when following the linux build instructions:
CMake Warning (dev) at cuda_compile_ptx_1_generated_cuda_gvdb_copydata.cu.ptx.Release.cmake:77:
Syntax Warning in cmake code at column 56
Argument not separated from preceding token by whitespace.
This warning is for project developers. Use -Wno-dev to suppress it.
nvcc fatal : Stray '"' character
CMake Error at cuda_compile_ptx_1_generated_cuda_gvdb_copydata.cu.ptx.Release.cmake:214 (message):
Error generating
/tmp/gvdb-voxels-master/build/gvdb_library/cuda_compile_ptx_1_generated_cuda_gvdb_copydata.cu.ptx
make[2]: *** [CMakeFiles/gvdb.dir/build.make:65: cuda_compile_ptx_1_generated_cuda_gvdb_copydata.cu.ptx] Error 1
make[1]: *** [CMakeFiles/Makefile2:67: CMakeFiles/gvdb.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
The text was updated successfully, but these errors were encountered: