…/configure --with-config-file=‘my_config_file.ac9’ > log
./my_config_file.ac9: line 334: abinit_moddir: command not found
configure: WARNING: forcing MPI level to 2 might make the build fail
configure: WARNING: Fortran file extension could not be changed
configure: WARNING: some advanced Fortran tests may fail
configure: error: in /home/dprai/Installed_Software/abinit-9.0.4/build': configure: error: unable to compile a simple Fortran module See config.log’ for more details config.log (65.4 KB) config.log (65.4 KB)
A possible mistake in your .ac9 file might be some space characters around an equal sign. There must be none, because this file must be readable by a shell script.
Another possibility is that pointed by @jmbgmx : if you set wrong Fortran flags, the Fortran compiler will not be detected correctly. By policy, the configure script is forced to continue, even if it should fail telling you that the Fortran compiler is broken.
There are not only inconsistencies in your ac9 file but also some syntax errors…
At first, you don’t need to configure all the variables…
If all dependencies are well installed with apt ( HDF5 / Netcdf / libXC / lapack / blas libraries and MPI libraries for parallel ), a “minimal” ac9 file looks like :