Open ronniyjoseph opened 4 years ago
I think your C compiler is not linked to openmp
when you run pip install
. What is your version of gcc
?
hmm I have gcc version 7.4.0
If you're on OSX, the default clang compiler does not link to openmp any more, which is very weird and annoying. You can either install your own gcc with macports or homebrew or whatever, or you can install gcc with conda
, and use that.
Yes, I think @piyanatk ran into this issue earlier.
So I don't get this issue if I compile the corrcal C library myself (with all linking options as provided in the original code), and do the import manually etc.
So I've been trying to find out if there is a way I can force setup to tell me what compiling command it using, but to no avail. Any suggestions?
@ronniyjoseph try
pip install -vvv .
This should print the compiler command that pip is using.
@steven-murray The thing is that @ronniyjoseph is on Linux though, which is why this is very confusing. I have no issue fresh install it on enterprise.
Oh OK, that is super strange then. What OS are you on @ronniyjoseph ? Yes, the -vvv
option will print out A LOT. Sometimes I've found that the -fopenmp
flag has to be set in two places in the setuptools.Setup
compilation command. So I have it in extra_compile_args
and also extra_link_args
. Is that the case here?
We are only using extra_compile_args
. @ronniyjoseph, Can you try adding extra_link_args
with -fopenmp
flag to setup.py. It should be added somewhere between line 31 to 34.
@ronniyjoseph Were you able to resolve the issue?
I am indeed on ubuntu. I probably have to add extra extra flags. But even when I add all flags from the original compile command I get nada.
So for now I went back to manually compiling and setting the path myself
From #32, I suspect that @ronniyjoseph did python setup.py install
. Are you?