Closed Akramz closed 5 years ago
Thanks for reporting your issue. Since the problems started when you did an upgrade, the most likely cause is that your python and c compiler where not updated at the same time. Compiled python modules like pybufr-ecmwf really need to be compiled by a c-compiler (and associated fortran compiler) that was the exact same one as the one that was used to compile the python interpreter itself. For MacOS the only way I could get it working was to use homebrew to install both python and a matching gcc/gfortran combination. So could you try this on your side? i.e. if needed reinstall homebrew compatible with Mojave. Then re-install the latest python, the latest gcc/gfortran, both from homebrew, and then rebuild the pybufr-ecmwf module? What happens in this case?
Thank you for answering,
I've solved the error by installing GCC-8.2 from source and used it to install pybufr_ecmwf.
Other: I got a few errors when I tried re-doing the installation steps after updating brew, when running:
brew tap Homebrew/python
and
brew install homebrew/python/numpy --with-python3
They Give back:
Error: homebrew/python was deprecated. This tap is now empty as all its formulae were migrated.
Again, thank you very much for your efforts.
Hi, thanks for reporting back. So to help other users, could you explain how you solved the brew error? Or you did not and just ignored it? From the error message I get the impression that there has just been a name-change (but I cannot test it, since I have no Mac system at hand for testing).
I'm working with Conda environments all the time, and python uses anaconda's python path by default (even with no environment activated), so I just ignored this error and it works fine.
First of all, Thank you for your valuable work, I always use your library to decode BUFR.
My Problem happened after i upgraded my OS to Mojave, at first a noticed that the library stopped importing correctly, producing this error:
I then proceeded to reinstall it following the usual steps described in here, it gave back this error:
After running tests:
Ran 65 tests in 6.096s
Is there a way to fix this ?