PLEASE HELP!! cannot compile em_real when nested domains are selected

[zhw]

Hi members,

Hope everyone is doing great. I have been stuck for more than two weeks, please help me!

I was trying to follow the ARW online tutorial on how to compile em_real. I selected 32 at ./configure and chose 0. em_real can be compiled successfully. I can run simulations successfully.

However, when I selected 32 at ./configure and chose 1 (basics), I got an error message saying that Fatal Error: cannot open module file 'module_io.mod' for reading at (1) no such files or directory. I have attached the log.compile for your reference. I could not choose 34 either, as when I tried which CC, my bash does not return anything, though I have set export CC='gcc' correctly.

I have successfully installed all the libraries in needed, and stored them at correct locations:

# Path Settings
export WRF_EM_CORE=1
export DIR=/home/Build_WRF/LIBRARIES
export CC=gcc
export CXX=g++
export FC=gfortran
export FCFLAGS=-m64
export F77=gfortran
export FFLAGS=-m64
export JASPERLIB=$DIR/grib2/lib
export JASPERINC=$DIR/grib2/include
# Unactivate this to install NetCDF-Fortrand
#export LDFLAGS=-L$DIR/grib2/lib
#export CPPFLAGS=-I$DIR/grib2/include

## NetCDF
export PATH=$DIR/netcdf/bin:$PATH
export NETCDF=$DIR/netcdf
export LIBS="-lnetcdf -lz"

# Activate this to install NetCDF-Fortrand
export LDFLAGS=-L$DIR/netcdf/lib
export CPPFLAGS="-I$DIR/netcdf/include -fcommon"
export FFLAGS=-fallow-argument-mismatch
export FCFLAGS=-fallow-argument-mismatch

# netcdf library
export NETCDF=/home/Build_WRF/LIBRARIES/netcdf

# WPS ungrib
export LD_LIBRARY_PATH=/home/Build_WRF/LIBRARIES/grib2/lib:$LD_LIBRARY_PATH

# Post Processing set-up
export LD_PRELOAD=/home/miniconda3/lib/libstdc++.so.6


I would greatly appreciate if anyone can help me with this!!


Best regards,
ZHW

 

[zhw]

I was able to locate the position of module_io.mod, it is at: /home/WRF/frame/module_io.mod, but when compiling it, WRF cannot find it. Please help me! Thanks!

 

[islas]

Between builds did you do a `./clean -a`?

Also, I noticed you are running v4.3.3. If your situation allows it, it may be worth trying to upgrade to the latest release as often issues with older versions have been addressed in newer versions.

 

[zhw]

Between builds did you do a `./clean -a`?

Also, I noticed you are running v4.3.3. If your situation allows it, it may be worth trying to upgrade to the latest release as often issues with older versions have been addressed in newer versions.

Hi, thank you for your reply! yes, I did do ./clean -a, but it didn't work out...

Thanks for your suggestions! I tried the latest version by git clone it, but I am still unable to compile successfully ... i will attach the new log.compile.txt below. Any help will be greatly appreciated!

 

[islas]

That's unusual.. Especially as you were able to compile before with a `./clean -a` I would expect most issues like this to resolve. Would you be able to use the new `./configure_new` and `./compile_new`? This does use CMake and places your normal workflow under install/ by default but could provide an alternate solution. If that also fails I suspect it could be something in the environment. Note that you will NEED to do a ./clean -a before using the newer build system as the old one leaves a bunch of compiled files in the directories otherwise that are not exactly compatible.

In the meantime I'll continue to see if I can narrow down the issue.