Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

WRF-Chem compilation error

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

farahani

New member
Hello,

I try to compile WRF-Chem 3.9.1 on Cheyenne and here is my settings in .bashrc:

export WRF_CHEM=1
export WRF_EM_CORE=1
export WRF_KPP=1
export WRF_NMM_CORE=0
export WRFIO_NCD_LARGE_FILE_SUPPORT=1
export FLEX_LIB_DIR="/usr/lib64"
export YACC="/usr/bin/yacc -d"

and I did
./clean -a
rm compile.log
./configure -D
./compile -j 4 em_real >& compile.log &

But I got these errors:

nup_em.f90(68): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_INITIALIZE_REAL]
real_em.f90(10): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_INITIALIZE_REAL]
real_em.f90(10): error #6580: Name in only-list does not exist or is not accessible. [WRFU_INITIALIZE]
real_em.f90(10): error #6580: Name in only-list does not exist or is not accessible. [FIND_MY_PARENT]
real_em.f90(10): error #6580: Name in only-list does not exist or is not accessible. [FIND_MY_PARENT2]
nup_em.f90(68): error #6580: Name in only-list does not exist or is not accessible. [WRFU_INITIALIZE]
real_em.f90(282): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_INITIALIZE_REAL]
real_em.f90(367): error #6404: This name does not have a type, and must have an explicit type. [INTERNAL_TIME_LOOP]
make[1]: [nup_em.o] Error 1 (ignored)
make[1]: [real_em.o] Error 1 (ignored)
ifort: error #10236: File not found: 'real_em.o'
make[1]: [em_real] Error 1 (ignored)
---> Problems building executables, look for errors in the build log <---


Any suggestion? my address on Cheyenne is:
/glade/scratch/aamiri/ana/WRFV3

Thank you,
Ana
 
Hello Ana,

(I imagine you've solved this by now, but I wanted to leave the solution for future users (including myself) who encounter this error)

I think this issue is resolved by removing -j or setting -j to 1. For some reason compiling on multiple processors doesn't always work.

Alex
 
Top