-
Notifications
You must be signed in to change notification settings - Fork 27
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
undefined symbol: gsl_rng_uniform_int #29
Comments
Hi Adrian, Looks like it's not linking properly. Can you try rerunning the above but with I was not able to repro this on my linux machine, and the Travis builds are working properly, also on linux. I'm not sure what could be different about your setup. Best, |
Hi Scott, Thanks for your quick reply. Incorrect linking was my first guess, too, but unfortunately I'm not familiar enough with the Cython framework to identify the cause of the problem. Here are the logs from both machines: One major difference is that the code is compiled with clang on macOS whereas gcc is used on linux. Best, |
Thanks for sharing. I don't see anything particularly strange in the logs... no errors in compilation or linking reported. Why don't you try this instead. First install GSL manually, e.g. on Ubuntu:
(You could also do this via Then install pypolyagamma by linking against the system-wide GSL library (rather than downloading GSL and compiling necessary source files, as the master branch does). You can do this with the
In the future, I'd like to move PyPolyaGamma to this installation approach, but I'm not yet convinced it will work (more) reliably for everyone. |
Hi Scott, good news: it's running -- yet, I still don't know what the problem was. It turned out that everything works fine if I run the code in a conda environment. Apparently, the linking problem does not occur there. However, I used had to use the master branch (or, alternatively, simply "pip install pypolygamma") since the proposed condagsl approach didn't work either. By the way, while testing, I also noticed that the pip installation only works with Python 3.6 but not with 3.7. The error looks pretty much like the one described here: Anyway, thanks a lot for your help! |
Hi Scott,
Thanks for sharing your code. Unfortunately, I am having problems executing it on my Linux machine. While everything works fine on macOS, I get the following error on Linux:
The minimal code to reproduce the error is:
As I said before, the above runs perfectly fine on macOS. Do you have any clue what is going on here?
Best regards,
Adrian
The text was updated successfully, but these errors were encountered: