Unrecognised flag failure on ARCHER during "fcm build" to generate RADAERv2 small executables for v7.3
|Reported by:||gmann||Owned by:||gmann|
Dear NCAS-CMS helpdesk,
Yesterday, I have been working to generate the necessary
4 small executables (qxsetup, qxcombine, qxhistrep, qxpickup)
which are required to be "pre-built" (on the target machine
architecture, ARCHER) before v7.3 UM-UKCA simulations can run
with RADAERv2 translating the GLOMAP aerosol properties into
3D aerosol optical properties (Qscat, Qext, asymetry) to enable
their radiative effects to be enacted in the atmosphere model.
This required the execution (on PUMA) of 4 "build" scripts (one
for each of those required executables such as build_qxsetup.sh)
which first extract the required from the FCM branch on PUMA
(in this case v7.3_HG3r2_mergCJ_nprim_Radv2) to
$HOME/um/um_extracts/myqx*_build/ and then copy over to
ARCHER (to /work/n02/n02/<user>).
Once those PUMA extract-and-copy scripts have been executed, the
final step required to generate the 4 files (qxsetup, qxcombine
qxhistrep and qxpickup) is then to (on ARCHER) actually run an
"fcm build" command from within the myqxsetup_build directory
(for example) which should, as explained by Mohit Dalvi
from his instructions [based on what Nicolas Bellouin did],
then produce the requireed corresponding small executable in
the bin sub-directory (in this case the file is qxsetup).
The syntax advised by Mohit was as follows:
fcm build -j 4 > bld.out 2>&1
so that the file "bld.out" then contained the log file on
how the build progressed.
I did this last night and it seemed to begin to progress fine,
the "fcm build" being successfully recognised.
However, the command failed reporting that the "-P" flag on the
compilation was not recognised.
I expect this error is either a case of me needing to run
some initial command to enable some different functionality
of the compiler from the command line, or alternatively it
may be that the build will only work if it is submitted to
the serial nodes with the required headers and
environment-variables set as needed.
I have pasted below the output from the bld.out file.
Is it just a case of setting something differently in
my .profile for a module to be loaded or similar to
enable the required functionality of the compiler?
Or perhaps a different compiler operation is set by
default at the command line compared to running in
the serial queue with the settings as specified
within the UM scripts?
Thanks a lot for your help with this,
Build command started on Tue Mar 28 23:37:39 2017.
→Parse configuration: start
Config file (bld): /fs2/n02/n02/gmann/myqxsetup_build/cfg/bld.cfg
→Parse configuration: 4 seconds
→Setup destination: start
→Setup destination: 0 second
→Setup build: start
→Setup build: 97 seconds
No. of files scanned for PP dependency: 2889
ftn-2105 crayftn: ERROR in command line
"-P" is an invalid command-line option.
[FAIL] ftn -P -E -DC_LOW_U=c_low_u -DFRL8=frl8 -DLITTLE_END=little_end -DC_LONG_INT=c_long_int -DMPP=mpp -DLINUX=linux -DXT4=xt4 -DSETUP=setup -DUTILHIST=u
tilhist -DUTILS=utils -I/fs2/n02/n02/gmann/myqxsetup_build/inc rcf_parvars_mod.F90 failed (1) at /fs2/y07/y07/umshared/software/fcm-2016.12.0/bin/../lib/FC
M1/BuildSrc.pm line 751