-
Notifications
You must be signed in to change notification settings - Fork 18
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
CMake Error at patches_generated_extract_patches.cu.o.cmake:207 #2
Comments
Hi, Thanks for taking the time to compile and test the code. I have not come across this issue, however I do see a ton of warnings when I compile for CUDA which hints towards something not being done 100% correctly. Since you can reproduce the error I have the following suggestions, if you want to help :). In any way thank you very much for the interest and the time.
In any way if you just want to use the library you can disable cuda for compiling the extension and the wall clock time cost will not be that much. Maybe ~20%. Every convolution etc will still be happening on the GPU just the patch extraction will be happening on the CPU which is not that slow. I will also try to reproduce the error and will post here if I manage. Cheers, |
Hi, sorry to have just gotten back to this. I did as you suggested and included both Thanks for your help! |
Hi, I am closing the issue because I can't reproduce it. Feel free to reopen or open a new one if you have problems. Cheers, |
I'm building your ats repository inside of a Docker container based on the latest tensorflow gpu image with this Dockerfile:
In order to build, I've set the
"default-runtime":"nvidia"
.Some other version info:
An error is encountered at cmake:
I am confused because I see in
ats/ops/extract_patches/CMakeLists.txt
youset(CMAKE_CXX_STANDARD 11)
, but the error is related to "C++ versions less than C++11 are not supported."? I'm not well versed in c++, is this something you've run into previously? How can I move forward?CPU version compiles and tests successfully.
The text was updated successfully, but these errors were encountered: