Hello,
Since Feb 6, our conda environment no longer works when compiling Fortran extensions with f2py.
This is due to a recent setuptools release (>= 81.0 on 6 february), which breaks the f2py build process (Fortran extensions fail to compile, even though the toolchain worked before). Downgrading setuptools fixes the problem.
Here is a quick fix (temporary workaround) :
In croco_pytools/env.yml, pin setuptools to a version < 81.0, for example:
dependencies:
- setuptools<81.0
or after environment creation, if you use conda : conda install "setuptools<81.0"
thanks for testing this and for the feedback. On our side, with setuptools<81.0 pinned, we do not reproduce the rank mismatch error with pytools 2.0.2 or 2.0.3 — f2py extensions compile and run as expected.
To help us understand the difference, could you please confirm:
your Python version
NumPy version
exact setuptools version after pinning
compiler (gfortran version)
platform (OS version)
If possible, the error traceback would also be helpful.
There may be an additional dependency interaction beyond setuptools, and this information should allow us to reproduce the issue.
I reproduced the rank mismatch error. when I shift it to Intel it is solved and created toolsf.cpython-39-x86_64-linux-gnu.so . still thinking about mpiifort/mpiifx.
I had this kind of issue.
Did you made a new conda/mamba croco_pyenv environnement (ex croco_pyenv_203), using the env.yml ( + downgrade specific setuptools as mentionned above) when you tried 2.0.2 or 2.0.3 ?
On my side, it fixed the rank mismatch error.
Hi, @gcambon@Konstantinos_K
Build toolsf module WITHOUT numpy or f2py (setuptools 82.0.0 or greater than) build_pure_new.py (5.0 KB)
Currently I haven’t found any errors yet. I saw someone deleted my last post. I don’t know why. if it’s useful or not?
I hope it will work.
merci