Problem building 10.6.7

Building Abinit
1

On typing ./configure, with no .ac9 file present, I get

±-----------------------------------------------------------------+
| Your environment does not provide mandatory libraries, |
| but we can build them for you. |
| Check the list above, all the ones marked as fb,for fallbacks, |
| will be installed locally. |
| |
| To proceed, you can run: |
| make |
| |
| Or you can install/load those libraries and rerun |
| configure |
| |
±-----------------------------------------------------------------+

~/source/abinit-10.6.7> make
make all-recursive
make[1]: Entering directory ‘/home/ian/source/abinit-10.6.7’
Making all in fallbacks
make[2]: Entering directory ‘/home/ian/source/abinit-10.6.7/fallbacks’
make[2]: *** No rule to make target ‘all’. Stop.
make[2]: Leaving directory ‘/home/ian/source/abinit-10.6.7/fallbacks’
make[1]: *** [Makefile:1608: all-recursive] Error 1

2

I notice that we forgot to include the configure file in the source tarball of 10.6.7. And so, from the source directory, try do do:
./config/scripts/makemake

Then you can try again to do ./configure and make. Make sure your internet connection is on.

If that doesn’t solve it. Can you please tell me what is the content of the fallbacks directory?

@gonze We should generate again the 10.6.7 tarball to include the configure script in it.

3

Dear Gabriel, I just checked: the Release v10.6.7 · abinit/abinit · GitHub page mentions “DOWNLOAD : Source code (with configure)”, that points correctly to forge.abinit.org/abinit-10.6.7.tar.gz that contains the configure. Then, the instructions at docs.abinit.org/installation can be followed, possibly skipping step 3 … By the way, the problem might come from downloading instead the source code from the Github “Assets”. It is mentioned above the Assets that “NB : The files “Assets” delivered below automatically by github are not to be used by normal users …” .
Best regards,
Xavier

4

Dear @iangay
I was able to reproduce your problem. I may not have the best way to fix it, but here is a temporary solution that worked for me:

  • From the download page, download the source code under “Assets”

  • Once it is unpacked, from the source directory, generate the configure script:
    ./config/scripts/makemake

  • Run the configure script: ./configure

  • Build the binaries: make

5

Thank you for your suggestion, unfortunately it doesn’t work

~/source/abinit-10.6.7> ./config/scripts/makemake
[makemake] Starting at 2026/06/22 17:50:41 +0000
[makemake] -------------------------------------
[makemake] === Source tree consistency ===
[makemake] Enabling write permission for all dirs & files
[makemake] === Build system update ===
[makemake] Resetting configuration dumper
[makemake] Generating macros for the Autotools
[makemake] Generating macros for dumpers
[makemake] Generating macros for environment variables
[makemake] Generating macros for command-line options
[makemake] Generating macros for hints
[makemake] Generating macros for debugging
[makemake] Generating macros for default optimizations
[makemake] Generating macros for per-directory optimizations
[makemake] Generating macros for core libraries
[makemake] Generating macros for feature triggers
[makemake] Generating macros for configure output
[makemake] Generating source split symlink maker
[makemake] === Source tree update ===
[makemake] Removing build examples
[makemake] Generating build examples
[makemake] Generating CPP option dumper
[makemake] —> running ./abisrc.py makemake > abisrc.stdout 2> abisrc.stderr

   ****************************************************************
   ***                     FATAL ERROR!                         ***
   ****************************************************************
   *** The abisrc.py script returned a non-zero exit status.    ***
   *** This usually means that the script found subroutines or  ***
   *** functions that are not declared inside modules or that   ***~/source/abinit-10.6.7> ./
[makemake]   Generating source split symlink maker
[makemake] === Source tree update ===
[makemake]   Removing build examples
[makemake]   Generating build examples
[makemake]   Generating CPP option dumper
[makemake] ---> running ./abisrc.py makemake > abisrc.stdout 2> abisrc.stderr

       ****************************************************************
       ***                     FATAL ERROR!                         ***
       ****************************************************************
       *** The abisrc.py script returned a non-zero exit status.    ***
       *** This usually means that the script found subroutines or  ***
       *** functions that are not declared inside modules or that   ***
       *** there is a syntax error in the Fortran code or a bug     ***
       *** See above error message.                                 ***
       ****                                                         ***
       *** Please note that procedures outside Fortran modules are  ***
       *** not allowed any longer. See abisrc.stderr for details    ***
       *** about the errors.                                        ***
       ****************************************************************
[makemake] Aborting now

   *** there is a syntax error in the Fortran code or a bug     ***
   *** See above error message.                                 ***
   ****                                                         ***
   *** Please note that procedures outsid[makemake]   Generating source split symlink maker
[makemake] === Source tree update ===
[makemake]   Removing build examples
[makemake]   Generating build examples
[makemake]   Generating CPP option dumper
[makemake] ---> running ./abisrc.py makemake > abisrc.stdout 2> abisrc.stderr

       ****************************************************************
       ***                     FATAL ERROR!                         ***
       ****************************************************************
       *** The abisrc.py script returned a non-zero exit status.    ***
       *** This usually means that the script found subroutines or  ***
       *** functions that are not declared inside modules or that   ***
       *** there is a syntax error in the Fortran code or a bug     ***
       *** See above error message.                                 ***
       ****                                                         ***
       *** Please note that procedures outside Fortran modules are  ***
       *** not allowed any longer. See abisrc.stderr for details    ***
       *** about the errors.                                        ***
       ****************************************************************
[makemake] Aborting now

   *** there is a syntax error in the Fortran code or a bug     ***
   *** See above error message.                                 ***
   ****                                                         ***
   *** Please note that procedures outside Fortran modules are  ***
   *** not allowed any longer. See abisrc.stderr for details    ***
   *** about the errors.                                        ***
   ****************************************************************

e Fortran modules are  ***
   *** not allowed any longer. See abisrc.stderr for details    ***
   *** about the errors.                                        ***
   ****************************************************************

[makemake] Aborting now

The content of abisrc.stderr is

Traceback (most recent call last):
File “/home/ian/source/abinit-10.6.7/./abisrc.py”, line 14, in
from fkiss import termcolor
ModuleNotFoundError: No module named ‘fkiss’

6

@gonze You are right! But now I think there is something wrong with the source code with configure. It looks like the file fallbacks/Makefile.am is missing, which is why the configure script fails to produce the Makefile for the fallbacks.

The user cannot generate this file, because the package is missing other files that are necessary to run the autogen.sh or the makemake scripts: in particular the fkiss package is missing.

7

@iangay The reason this is failing is that you need to download the correct version of the source files (the one under “Assets”). Here is the link.
We are working on fixing this, sorry!

8

In the version at that link, the top level configure file is missing!

9

Yes, this is normal. That is why you need to generate the configure file by running either ./autogen.sh or ./config/scripts/makemake

10

With this procedure, building fallbacks started, then died with

Fatal Error: Cannot open module file ‘netcdf.mod’ for reading at (1): No such file or directory

11

Is it possible that this error happens during the Abinit compilation, after the fallbacks are built?

I found a couple of problems in the configure script that will be fixed in a future release. One of those problems is that the version number for netcdf4_fortran is incorrect…

I suggest writing a configuration file whose name should be given by the result of the command:
echo `hostname -s`.ac9

For example, my configuration file is named Beatrix.ac9 and it looks like this:

with_mpi="/opt/homebrew/"
enable_mpi_io="yes"

with_fallbacks="yes"

fb=/Users/antonius/Software/Abinit/abinit-git/build1/fallbacks/install_fb/gnu/13.2/
with_hdf5=${fb}/hdf5/default/
with_netcdf=${fb}/netcdf4/default/
with_netcdf_fortran=${fb}/netcdf4_fortran/default/
with_libxc=${fb}/libxc/default/

with_fft_flavor="fftw3"

LINALG_LIBS="-L/opt/homebrew/Cellar/lapack/3.12.1/lib/ -llapack -lblas -L/opt/homebrew/Cellar/scalapack/2.2.3/lib/ -lscalapack"
LINALG_FCFLAGS="-I/opt/homebrew/Cellar/lapack/3.12.1/include/"

Of course, you should adapt this file to yout platform. In my case, my fortran compiler is /opt/homebrew/bin/mpif90 and I use the fftw library in /opt/homebrew/Cellar/fftw/3.3.11

12

No, the libxc fallback built apparently ok, then that message appeared when it started to build the netcdf fallbacks.

13

Please provide a bit more context for the output that you see, leading to the error message.