-
Notifications
You must be signed in to change notification settings - Fork 370
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
Can't build v0.5 - openmp? #208
Comments
Oops, just saw the note about using pytorch 1.6. Unfortunately, even after upgrading to 1.6 (and trying 1.7), I still get the same error. Interestingly, I was able to build ME 0.5 on my Jetson AGX with no problems. Tried to replicate python and pytorch versions on my x86-64 machines, but no luck. |
Hmm, the setup.py file in MinkowskiEngine does not specify fopenmp for nvcc compilation. On my machine, pytorch is not adding
|
Appears to work fine for me when I use Anaconda on my system. And since it also works without Anaconda on my ARM system, I'm guessing I have something wrong on my end. |
Same issue here with Ubuntu 18.04, CUDA 10.2 and pytroch 1.6, I don't use Ninja, maybe that's the issue?
|
Yes, I can confirm, building with Ninja fixes the issue. @chrischoy you probably want to make it mandatory (or fix this weird problem that make add -fopenmp to the compilation flags...) |
same issue, Ubuntu 18.04, CUDA 11.2, pytorch 1.8.1 - wasn't using ninja; then installed 1.10.2 and I agree - should make it clear in README that |
Hi @plusk01 , I believe pytorch c extensions use ninja by default. |
Hi @chrischoy - on my Ubuntu 18.04 machine i did not have |
Thanks, I specified the ninja installation in the README as well as the setup script with |
@haiduo I have the same issue. Did you resolve it? |
Yes, you can refer to #495 (comment) |
@haiduo Thank you. It works now. |
I can build the current
master
branch, butv0.5
fails for me.I have:
Here's some notable output of running
python setup.py build
:The text was updated successfully, but these errors were encountered: