...
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 |
Successful compilation
After a successful compilation, the OpenIFS executable, master.exe
, can be found in the 'make/build
' subdirectory:
Code Block |
---|
% ls
build fcmcfg
% ls build
bin include o
% ls build/bin
master.exe |
The 'build
' subdirectory is generated by FCM. The build/include
directory contains all the files referenced in the code by a '#include
' statement. This includes the Fortran interface block files which are auto-generated by FCM and end in .intfb.h
. The build/o
directory contains all the compiled object files. The OpenIFS build does not place any additional files in the src
directory (known as building 'out of source').
Compilation problems
If you get the message:
Code Block |
---|
fcm make -f fcmcfg/oifs.cfg /bin/ksh: fcm: not found [No such file or directory] |
...