Extended MODFLOW installation: test-drive needed?

[geo-admin-joe]

I'm trying to install Extended MODFLOW 6 using the installation instruction from the user guide. When I execute meson setup builddir -Ddebug=false -Dextended=true --prefix=$(pwd) --libdir=bin, I get the following output:

(mf6xtd) root@PC12365:~/modflow6# meson setup builddir -Ddebug=false -Dextended=true --prefix=$(pwd) --libdir=bin --reconfigure
Regenerating configuration from scratch: Build directory has been generated with Meson version 1.7.1, which is incompatible with the current version 1.8.1.
The Meson build system
Version: 1.8.1
Source dir: /root/modflow6
Build dir: /root/modflow6/builddir
Build type: native build
Project name: MODFLOW 6
Project version: 6.7.0.dev2
Fortran compiler for the host machine: gfortran (gcc 15.1.0 "GNU Fortran (conda-forge gcc 15.1.0-2) 15.1.0")
Fortran linker for the host machine: gfortran ld.bfd 2.43
Host machine cpu family: x86_64
Host machine cpu: x86_64
Message: Profile: release
Message: Compiler ID: gcc
Message: Extended build: true
Found pkg-config: YES (/opt/miniforge/envs/mf6xtd/bin/pkg-config) 0.29.2
Run-time dependency petsc found: YES 3.22.3
mpifort found: YES (/opt/miniforge/envs/mf6xtd/bin/mpifort) 5.0.7
Run-time dependency MPI for fortran found: YES 5.0.7
Run-time dependency NetCDF for fortran found: YES 4.6.1
Compiler for Fortran supports arguments -fall-intrinsics: YES
Compiler for Fortran supports arguments -pedantic: YES
Compiler for Fortran supports arguments -cpp: YES
Compiler for Fortran supports arguments -Wcharacter-truncation: YES
Compiler for Fortran supports arguments -Wno-unused-dummy-argument: YES
Compiler for Fortran supports arguments -Wno-intrinsic-shadow: YES
Compiler for Fortran supports arguments -Wno-maybe-uninitialized: YES
Compiler for Fortran supports arguments -Wno-uninitialized: YES
Compiler for Fortran supports arguments -D__linux__: YES
Compiler for Fortran supports arguments -ffpe-summary=overflow: YES
Compiler for Fortran supports arguments -ffpe-trap=overflow,zero: YES
Compiler for Fortran supports arguments -D__WITH_PETSC__: YES
Compiler for Fortran supports arguments -D__WITH_MPI__: YES
Compiler for Fortran supports arguments -D__WITH_NETCDF__: YES
Message: MODFLOW 6 executable name: mf6
Message: MODFLOW 6 shared library name: libmf6
Message: ZONEBUDGET 6 executable name: zbud6

Found CMake: /usr/bin/cmake (3.28.3)
WARNING: CMake Toolchain: Failed to determine CMake compilers state
Run-time dependency test-drive found: NO (tried pkgconfig and cmake)
Program mpiexec found: YES (/opt/miniforge/envs/mf6xtd/bin/mpiexec)
Build targets in project: 5

MODFLOW 6 6.7.0.dev2

  User defined options
    debug   : false
    extended: true
    libdir  : bin
    prefix  : /root/modflow6

Found ninja-1.12.1 at /opt/miniforge/envs/mf6xtd/bin/ninja

Notice the line Run-time dependency test-drive found: NO (tried pkgconfig and cmake).

What is the easiest way to install the Run-time dependency test-drive? I tried:

git clone https://github.com/fortran-lang/test-drive.git
cd test-drive
meson setup builddir --prefix=/opt/miniforge/envs/mf6xt
meson compile -C builddir

but I ran into more errors, like:

[6/13] Compiling Fortran object libtest-drive.so.0.5.0.p/src_testdrive.F90.o
../src/testdrive.F90:438:30:

  438 |     do it = 1, size(testsuite)
      |                              ^
Warning: 'testsuite.dim[0].ubound' is used uninitialized [-Wuninitialized]

and

[8/13] Compiling Fortran object test/tester.p/test_select.F90.o
FAILED: test/tester.p/test_select.F90.o test/tester.p/test_select.mod
gfortran -Ilibtest-drive.so.0.5.0.p -Itest/tester.p -Itest -I../test -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -O2 -g -ffree-line-length-none -fbacktrace -DWITH_QP=1 -DWITH_XDP=1 -Jtest/tester.p -o test/tester.p/test_select.F90.o -c ../test/test_select.F90
../test/test_select.F90:156:22:

  156 |     call run_selected(stub_collect, "not-available", unit, stat)
      |                      1
Error: Interface mismatch in dummy procedure 'collect' at (1): ALLOCATABLE mismatch in argument '_formal_0'
../test/test_select.F90:139:22:

  139 |     call run_selected(stub_collect, "always-fail", unit, stat)
      |                      1
Error: Interface mismatch in dummy procedure 'collect' at (1): ALLOCATABLE mismatch in argument '_formal_0'
../test/test_select.F90:121:23:

  121 |     call run_testsuite(stub_collect_bad, unit, stat)
      |                       1
Error: Interface mismatch in dummy procedure 'collect' at (1): ALLOCATABLE mismatch in argument '_formal_1'
../test/test_select.F90:103:23:

  103 |     call run_testsuite(stub_collect, unit, stat)
      |                       1
Error: Interface mismatch in dummy procedure 'collect' at (1): ALLOCATABLE mismatch in argument '_formal_1'

• What should I do?
• Is test-drive even rquired to use install/use MODFLOW?
• If so, what is the recommended way to install it?

[wpbonelli]

@geo-admin-joe test-drive is strictly optional. We use it for some unit tests, but meson will skip those otherwise. You are seeing the warning when meson fails to find it with pkg-config.

We have some docs on setting up test-drive here. I'm not sure about the error you're seeing. I do not think test-drive has been tested with recent gfortran versions.. I'll see if I can set that up. You might try using gfortran <=13?

[wpbonelli]

Just tried building test-drive with gfortran 15 (on macOS) and I see the same error. Adding --warnlevel=0 to the meson setup command fixes it, as I found advised here fortran-lang/test-drive#49.

Though I think we still need to put some work into the project's compiler compatibility, both gnu and intel..

[jdhughes-dev]

Test-drive works for me with gfortran-14 from homebrew on a Mac

[geo-admin-joe]

Thank you for the advice!

Since I know now that test-drive is optional and I'm not on a Mac, I'm not going to put further effort into this. After some other fixes, the installation and subsequent test (as described in the in the installation instructions) worked fine.