Build process assumes creation of .mod files. Fails with Cray compiler.

[trackstand]

Unlike a lot of other Fortran compilers, it seems that the Cray compiler does not produce a .mod file when it has built a module. It somehow encodes the information that would normally be in a .mod within the .o file.
Since the .o file is not put in the standard include directory (CONFIG/<CONFIG_NAME>/BLD/inc) the compiler can't find it and thus fails to find module definitions when processing USE statements.

[sga]

Hello. I had a quick look through the cray fortran man page and it seems you can override this behaviour if you include the '-em' option. Try it and let us know.
Steven

[trackstand]

Hi Steven, you're right. Always the way; I discovered this after I'd submitted the ticket. Using "-em -J." does the trick. Is there somewhere appropriate to document this?
Cheers, Andy.

[sga]

Hello Andy. I guess the best thing to do would be to add the fcm file you eventually end up with to the 3.3 release in some form.
That way it's available for people to use with the CRAY compiler. I'm assuming that you're trying to build on hector. There's one for the PGI compiler already, called arch-XT6_HECTOR.fcm. It has the options for the gnu programming module included but commented out. With so many different compilers on hector it may be best to add the cray options as comments as well.
Steven

[acc]

Solvable with compiler options. See for example ARCH/NOC/arch-XT6_HECTORcrayftn.fcm.
Ticket closed.