Closed tjtakys closed 7 months ago
I've been trying to correct a range of fortran compilation errors over the past several weeks without luck; something in the compilers changed in the last several years, and it has broken some components of RADEX or f2py.
Anyway, though, I don't see any clear error anywhere in your traceback, which is strange. Try leaving out the install_fjdu
command - see if you can get it to build without that (it's a separate, extra module)
Thanks for the quick reply!
I commented out line 137 of the setup.py file and run python setup.py install_radex install_myradex install
, but I got the following error, which seesms to be the same as above...
Traceback (most recent call last):
File "setup.py", line 136, in
Also, I tried to comment out line 136 of setup.py file, and ran python setup.py install_radex install
command, but i got the following alike error...
Traceback (most recent call last):
File "setup.py", line 135, in
you don't need to edit the code, just do:
python setup.py install_radex build install
instead of
python setup.py install_radex install_myradex build install
i.e., leave out the install_myradex
step.
Oh, sorry. Okey, I did python setup.py install_radex build install
, and the following error I got.
Traceback (most recent call last):
File "setup.py", line 137, in
huh, ok, so that did exactly the same thing, apparently. That's... not what I expected.
this error message isn't helpful; the full traceback you gave above is (a little) more helpful.
I don't quite get it - there isn't actually any error being reported by f2py.
I'm not sure what's going on here, so for the sake of keeping issues going that I have some hope of fixing, I'm closing this. Feel free to reopen if you have more information to share.
Hi, I'm working on Mac OS 10.15.7. I am sure I meet the requirements for installation, but I cannot. First, I installed gcc via
brew install gcc
, and also installed gfortran viaconda install -c anaconda gfortran_osx-64
. Versions of them are as follows.I hope you can help me.