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

[pramodsoni41]

time mpif90 -w -ffree-form -ffree-line-length-none -fconvert=big-endian -frecord-marker=4 -fallow-argument-mismatch -fallow-invalid-boz -fopenmp -c -O2 -ftree-vectorize -funroll-loops -w -ffree-form -ffree-line-length-none -fconvert=big-endian -frecord-marker=4 -fallow-argument-mismatch -fallow-invalid-boz -I../ioapi_share diffwrf.f ; \

diffwrf.f:50:7:

50 | use module_ext_internal
| 1
Fatal Error: Cannot open module file ‘module_ext_internal.mod’ for reading at (1): No such file or directory
compilation terminated.

real 0m0.149s
user 0m0.042s
sys 0m0.105s
make[3]: [diffwrf.f] Error 1 (ignored)
rm -f libwrfio_int.a
ar ru libwrfio_int.a io_int.o io_int_idx.o module_io_int_idx.o module_io_int_read.o
ar: creating libwrfio_int.a
ar: io_int.o: No such file or directory
make[3]: [libwrfio_int.a] Error 1 (ignored)
ranlib libwrfio_int.a
ranlib: 'libwrfio_int.a': No such file
make[3]: [libwrfio_int.a] Error 1 (ignored)
if [ -f ../../frame/pack_utils.o -a -f ../../frame/clog.o ] ; then \

 

[islas]

Hi @pramodsoni41, could you post the full build output as a file upload? I think that will potentially have additional information to explain this issue.

 

[wde0924]

Hi @islas I got something similar when compiling WRF with gfortran from `compile.log` as shown below:

time gfortran -w -ffree-form -ffree-line-length-none -fconvert=big-endian -frecord-marker=4 -fallow-argument-mismatch -fallow-invalid-boz -c -O2 -ftree-vectorize -funroll-loops -w -ffree-form -ffree-line-length-none -fconvert=big-endian -frecord-marker=4 -fallow-argument-mismatch -fallow-invalid-boz -I../ioapi_share diffwrf.f ; \
diffwrf.f:50:7:
50 | use module_ext_internal
| 1
Fatal Error: Cannot open module file ‘module_ext_internal.mod’ for reading at (1): No such file or directory
compilation terminated.
real 0m0.029s
user 0m0.012s
sys 0m0.013s

The attached files include my configure.wrf and compile.log.
In addition, I noticed there were errors 127 after the fatal error. Should I check with our system IT people for more clues about "time gfortran"?

Thank you for your suggestions and please let me know if you need additional info from me!!

 

[wde0924]

Okay, I manually removed the `time` command from the FC assignment statement (FC = time $(SFC)) in the configure.wrf file. Re-compiling WRF-chem without `time` command worked.

Still, the weird thing is that the `time gfortran` command worked perfectly when I tried to test it in the terminal separately, e.g., following the first test from Library Compatibility Tests Compiling WRF (with `time` in front). And, `time` is found on the server. But, somehow it triggered errors like `time: No such file...` when compiling WRF or WRF-Chem

 

[islas]

Interesting. Are you compiling in two different environments on the server, e.g. the tests in the login node and compiling WRF in the compute nodes? Another potential issue is if you're default shell environment and csh differ in commands available (./compile uses csh)

 

[wrfuser80]

Okay, I manually removed the `time` command from the FC assignment statement (FC = time $(SFC)) in the configure.wrf file. Re-compiling WRF-chem without `time` command worked.

Still, the weird thing is that the `time gfortran` command worked perfectly when I tried to test it in the terminal separately, e.g., following the first test from Library Compatibility Tests Compiling WRF (with `time` in front). And, `time` is found on the server. But, somehow it triggered errors like `time: No such file...` when compiling WRF or WRF-Chem

Just want to chime in that I also had this issue using GNU Fortran (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

The simple fix of removing 'time' from FC in configure.wrf file also allowed me to compile successfully.