-
Notifications
You must be signed in to change notification settings - Fork 33
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
Cannot find the ecCodes library when pip installing eccodes 1.3.X #54
Comments
Same here. |
Can confirm what the above posters found as well, works with 1.2.0 but fails with anything 1.3.x |
Tried some more tests and there appears to be some sort of conflict on RHEL-based systems: Amazon Linux 2 for example puts the libraries in a lib64/ directory (which fails) while Ubuntu does lib/ (which works). As a workaround I renamed lib64 to lib and added the lib path to LD_LIBRARY_PATH and it worked under AL2. Not idea but maybe that helps track down the root cause? |
Thanks! Updating the LD_LIBRARY_PATH is the only thing that worked for me (cluster on Cent OS) |
Changing versions didn't work for me. All I had to do was: From bindings.py in:
There was:
The findlibs package was the problem. |
@nfick's fix works for me on Linux, but on Windows it causes some strange DLL load warnings:
But |
Ubuntu 20.04, python 3.8 |
Before installing cfgrib, my ecmwflibs version is 0.4.3 Thanks to @CrayonAki |
Im getting a similar error when runner a docker file
|
by adding 'libeccodes-tools' it now seems to work |
What solved for me was REALLY to install ECMWFlibs, just because eccodes depends on this earlier library to work. The version of ECcodes does not matter! So, at Google Colab, you can do:
|
I'm working with someone who is trying to add cfgrib/eccodes to our build environment and is running into weird behavior. Sometimes they get the same error(s) mentioned here and other times the errors are slightly different and sometimes it works. Whether the environment works or errors out seems to be related to the order the packages are installed. The order the packages are installed shouldn't matter, right? There should be no reason you can't do Note: Some of the issues we're running into may be specific to us trying to use pyinstaller to bundle our environment into a distributed application. |
Just came across this. I think it would be very valuable if the eccodes library and the eccodes-python package would also be distinguishable when installing in a conda environment:
Because they have both the same name, |
Perhaps adding to @observingClouds, I had the same issue and the way to fix it was to install in order |
Here is what worked for me: |
Reproducer
results in
Downgrading to 1.2.0 works just fine
The eccodes package from conda is
eccodes conda-forge/linux-64::eccodes-2.21.0-he2bb022_1
Cleaning up:
The text was updated successfully, but these errors were encountered: