WRF-CHEM (no .exe files after WRF compilation) [SOLVED]

[Georgii Nerobelov]

Dear Sir/Madam.
I try to configure and compile WRF-CHEM after installation and several successful runs of WRF-ARW v.4.0. The issue is when I compile WRF after successful configuration via ./compile em_real >& compile.log executable files (real.exe, wrf.exe and others) are not generated. It can be clearly seen from the directory .../WRF_4.1.2/main where those files have to appear and from the compile.log (see attached file) where there is a string on the bottom ---> Problems building executables, look for errors in the build log <---. Moreover, there are several errors inside of the compile.log nature of which is unfamiliar to me. I suppose that probably the problem occurs due to KPP (Kinetic Pre-Processor) option which I decided to use before compiling.
Whole steps (configuration and compilation) were made using this WRF-CHEM Guide (https://ruc.noaa.gov/wrf/wrf-chem/Users_guide.pdf), chapter 2.2 Building the WRF-chemistry code. Compile.log and configure.wrf have been attached to the topic.
Please, give me an advice how to solve this issue :?: . I appretiate any help and thank you in advance.

ADDITION INFO:
WRF version - 4.1.2
gcc (v.4.4.7) and gfortran compilers (v.4.4.7)
netCDF v.4.1.3
hdf5 is in $PATH (-bash: /home/hirlam/sednersoft/hdf5/bin

Environment options I used before the WRF configuration:

export DIR=/data0/home/hirlam/WRF_TEST/Build_WRF/LIBRARIES
export CC=gcc
export CXX=g++
export FC=gfortran
export FCFLAGS=-m64
export F77=gfortran
export FFLAGS=-m64
export JASPERLIB=/data0/home/hirlam/WRF_TEST/Build_WRF/LIBRARIES/grib2/lib
export JASPERINC=/data0/home/hirlam/WRF_TEST/Build_WRF/LIBRARIES/grib2/include
export LDFLAGS=-L$DIR/grib2/lib
export CPPFLAGS=-I$DIR/grib2/include
export NETCDF=/data0/home/hirlam/WRF_TEST/Build_WRF/LIBRARIES/netcdf
export PATH="/data0/home/hirlam/WRF_TEST/Build_WRF/LIBRARIES/mpich/bin/:$PATH"
export EM_CORE =1
export NMM_CORE=0
export WRF_CHEM=1
export WRF_KPP=1
export YACC='/usr/bin/yacc –d'
export FLEX_LIB_DIR=/usr/lib64

WRF configuration options:

32. (serial) GNU (gfortran/gcc)
nesting = 1 (basic)

 

[kwerner]

Hi,
Are you certain that the compile log you attached is the correct one? I'm asking because you mention your paths in your post, but they don't match the paths in the compile log. You also said you were compiling V4.1.2, but the compile log is for V4.0.

The problem in the compile log you sent seems to be pointing to a missing HDF5 library. If that's the case, take a look at this post regarding a similar issue to see if it helps you to figure anything out:
https://forum.mmm.ucar.edu/phpBB3/viewtopic.php?f=37&t=8277&p=13914&hilit=hdf5#p13914

Does this same problem occur if you compile a non-chem version of WRF?

 

[Georgii Nerobelov]

Hi,
Are you certain that the compile log you attached is the correct one? I'm asking because you mention your paths in your post, but they don't match the paths in the compile log. You also said you were compiling V4.1.2, but the compile log is for V4.0.

The problem in the compile log you sent seems to be pointing to a missing HDF5 library. If that's the case, take a look at this post regarding a similar issue to see if it helps you to figure anything out:
https://forum.mmm.ucar.edu/phpBB3/viewtopic.php?f=37&t=8277&p=13914&hilit=hdf5#p13914

Does this same problem occur if you compile a non-chem version of WRF?

No,the WRF compilation with option WRF-CHEM=0 runs correctly. The problems star after turning on CHEM module (WRF-CHEM=1 in the configure.wrf file). And yes,you are absolutely right - the log file is not mine. I was searching for the same issue in the Internet yesterday and downloaded someones log file which replaced my log. I will attach the correct log in about 1.5 hour. Sorry,my bad

 

[kwerner]

Hi,
I am moving this topic to the WRF-Chem section of the forum, as this seems to only be applicable when you are trying to build wrf-chem (and not basic WRF). Unfortunately our group does not develop/support WRF-Chem, but hopefully someone who is knowledgeable with WRF-Chem will be able to respond to this sometime soon.

 

[Georgii Nerobelov]

As I wrote above I attached the wrong compile.log to the issue. Here is the right one (compile_for_WRF-CHEM.log) which I`ve got after the compilation of the WRF-CHEM v.4.1.2. The issue is described in the head of the topic. Any help is appreciated.
P.S. I`ve just replaced the wrong compile.log from the head of topic with the right one (compile_for_WRF-CHEM.log) as in this comment.

 

[Georgii Nerobelov]

I suppose that I’ve found a solution. Upgrading the version of gcc (from older to newer) helped in my case. But the successful compilation of WRF-CHEM was made on the different computer (my personal laptop vs computer cluster). So I don't really know if newer version of gcc is only one requirement in handling this issue.
Thank you very much for your support and quick response!