id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
395	Possible problem compiling ropp_fm with sunf95	Ian Culverwell	Dave Offiler Ian Culverwell	"ROPP8.0 beta reviewer Dave offiler (UKMO) found:
{{{

- ROPP_FM: sunf95 reports errors compiling test t_fascod.f90: sunf95 -I../build
    -O -m64 -ftrap=%none  -I/home/dave/ropp/ropp-8.0/sunf95/include  -moddir=./
    -M/home/dave/ropp/ropp-8.0/sunf95/include  -M../build -c -o t_fascod.o 
    t_fascod.f90

      USE ropp_utils
          ^          
    ""t_fascod.f90"", Line = 40, Column = 7: ERROR: Incorrect rank of actual 
     argument number 1 in the generic procedure call ""SIZE"".

      USE ropp_io
          ^       
    ""t_fascod.f90"", Line = 41, Column = 7: ERROR: Incorrect rank of actual 
     argument number 1 in the generic procedure call ""SIZE"".

      USE geodesy
          ^       
    ""t_fascod.f90"", Line = 318, Column = 9: ERROR: Incorrect rank of actual 
     argument number 1 in the generic procedure call ""SIZE"".

    f90comp: 397 SOURCE LINES
    f90comp: 3 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI
    Makefile:414: recipe for target 't_fascod.o' failed
    make[1]: *** [t_fascod.o] Error 1

  which causes the FM build to apprently fail. However, the library and module
  files are installed and ROPP_1DVAR uses the FM without further issues. There
  were no reported problems compiling any of the upstream modules being  flagged
  here, and the prvoud version of sunf95 did not report these errors, so this
  may be a strict compiler issue, rather than any real problem with  the ROPP
  code, but the occurrences of SIZE in the flagged modules should be checked.

}}}

There were no problems building sunf95 on a RHEL56 linux box, which compiled '''t_fascod.f90''' with nary a pause:
{{{
sunf95 -I../build -O -m64 -ftrap=%none -I/data/local/idculv/ROPP/sunf95/include
-moddir=./ -M/data/local/idculv/ROPP/sunf95/include -M../build -c -o t_fascod.o 
t_fascod.f90
}}} 

Why is it complaining about SIZE in a USE statement?  If it's a SIZE command in the particular module, why doesn't it complain all the the (many) other times that these modules are USEd?

Setting it as a task because I don't know if there's a problem here. "	task	new	minor	Whenever	ROPP (all)	7.1		sunf95 WinPC