...
Code Block |
---|
export OIFS_GRIB_API_DIR=$HOME/ecmwf/grib_api_gcc export OIFS_LAPACK_LIB=/usr/local/apps/lapack/lib |
Compiling OpenIFS
Once the environment variables are set, OpenIFS can be compiled (make sure you have edited your PATH environment variable to add the FCM installation /bin
directory). Assuming you are in the directory where the OpenIFS source code was unpacked:
Code Block |
---|
cd make
fcm make -f fcmcfg/oifs.cfg |
The command 'fcm make
' starts the compilation. The -f option specifies the location of the master configuration file for OpenIFS.
This generates output similar to:
Code Block |
---|
[init] make # 2012-12-20 19:59:59Z
[init] make config-parse # 2012-12-20 19:59:59Z
[info] config-file=...../make/fcmcfg/oifs.cfg
[info] config-file= - ...../make/fcmcfg/x86_64-gnu-opt.cfg
[done] make config-parse # 0.3s
[init] make dest-init # 2012-12-20 19:59:59Z
[info] mode=new
[done] make dest-init # 0.3s
[init] make build # 2012-12-20 20:00:00Z
[info] sources: total=2194, analysed=2194, elapsed-time=11.7s, total-time=32.2s
[info] target-tree-analysis: elapsed-time=9.8s
[info] compile targets: modified=2073, unchanged=0, total-time=1095.5s
[info] compile+ targets: modified=628, unchanged=0, total-time=1.6s
[info] ext-iface targets: modified=1247, unchanged=0, total-time=21.9s
[info] install targets: modified=120, unchanged=0, total-time=0.3s
[info] link targets: modified=1, unchanged=0, total-time=18.3s
[info] TOTAL targets: modified=4069, unchanged=0, elapsed-time=316.3s
[done] make build # 329.1s
[done] make # 329.8s
|
If you get the message:
Code Block |
---|
fcm make -f fcmcfg/oifs.cfg
/bin/ksh: fcm: not found [No such file or directory] |
you need to add the 'bin' directory of the unpacked FCM installation to your PATH environment variable:
Code Block |
---|
export PATH=$PATH:$HOME/fcm-2-3/bin |