Opened 18 months ago
Closed 16 months ago
#2977 closed help (answered)
Changing compiler on ARCHER
Reported by: | luciad | Owned by: | um_support |
---|---|---|---|
Component: | UM Model | Keywords: | |
Cc: | Platform: | ARCHER | |
UM Version: | 11.1 |
Description
Hi, I'm getting errors from fcm_make2_um when I try to run the suite 'u-bk837' on ARCHER. There are many errors which all look similar, which look like they do below.
[FAIL] ftn -oo/var_look_mod.o -c -I./include -s default64 -e m -J ./include -I/work/y07/y07/umshared/gcom/cce8.5.8/gcom6.6/archer_xc30_cce_mpp/build/include -I/work/y07/y07/umshared/shumlib/shumlib-2018.06.1/ncas-xc30-crayftn-8.5.8-craycc-8.5.8/openmp/include -O2 -Ovector1 -hfp0 -hflex_mp=strict -h omp /work/n02/n02/luciad/cylc-run/u-bk837/share/fcm_make_um/preprocess-atmos/src/um/src/control/top_level/var_look_mod.F90 # rc=1 [FAIL] ifort: error #10236: File not found: 'default64' [FAIL] ifort: command line warning #10157: ignoring option '-error_limit'; argument is of wrong type [FAIL] ifort: error #10236: File not found: 'm' [FAIL] ifort: command line warning #10006: ignoring unknown option '-J' [FAIL] ifort: command line warning #10006: ignoring unknown option '-Ovector1' [FAIL] compile 3.9 ! var_look_mod.o <- um/src/control/top_level/var_look_mod.F90
I think I've narrowed it down to being due to the suite using the intel compiler rather than the cray compiler, but I can't seem to work out how to change to cray. Is this something to do with including overrides in /home/umui/overrides ?
Many thanks in advance,
Lucia
Change History (4)
comment:1 Changed 18 months ago by dcase
comment:2 Changed 18 months ago by luciad
Hi dave,
I've changed the permission. You should be able to access those files now.
Thanks,
Lucia
comment:3 Changed 18 months ago by dcase
In your ~/.bashrc you have a couple of lines which change the modules that you're using. Specifically of issue is
module swap PrgEnv-cray PrgEnv-intel
If I were you, I'd take these out unless that absolutely have to be there for some reason. You can load modules on an app by app basis by editing the appropriate .rc files for each suite.
I'm going to test the build part of your suite myself, but it'll take an hour or so to run. I'll let you know if there are any issues, but I'd suggest for now that you edit the bashrc to remove the module loads/swaps and try again as a first step.
Dave
comment:4 Changed 16 months ago by grenville
- Resolution set to answered
- Status changed from new to closed
closed for inactivity
Lucia,
could I just ask you to give read permission to your ARCHER files
then I'll look at this tomorrow,
Dave