[MITgcm-devel] genmake2 and fflags

[Martin Losch]

Hi Jean Michel,

currently I want to use something like this:

FEXTRAFLAGS='-pi fullmsg  
exp=timestep_tracer,ilnblnk,ifnblnk,cycle_tracer,pressure_for_eos  
rexp=bar2,fool_the_compiler  
expin=timestep_tracer.F,fool_the_compiler.F,bar2.F,utils.F,cycle_tracer. 
F,pressure_for_eos.F'

for the sxf90 compiler for our SX8. These are all files that are  
always used (as far as I can see, either in model/src or eesupp/src).  
When I add this to FFLAGS in the opt file, all genmake2 fortran-tests  
fail (no netcdf, etc) because the compiler looks for the the files  
specified in expin=*.F before they are linked to the directory.
The FEXTRAFLAGS (or whatever name you prefer) will not be used  
anywhere and is empty by default, so it should not affect any other  
experiment (although I did not try). Maybe you want to test this on  
some of your experiments which you find critical? I am attaching my  
"new" genmake2 and the corresponding build options file to show an  
example usage. Tell me what you think.

Martin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: genmake2.gz
Type: application/x-gzip
Size: 21096 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-devel/attachments/20070926/6bb754ef/attachment.gz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SUPER-UX_SX-8_sxf90+mpi_awi.gz
Type: application/x-gzip
Size: 1126 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-devel/attachments/20070926/6bb754ef/attachment-0001.gz>
-------------- next part --------------

On 26 Sep 2007, at 04:32, Jean-Michel Campin wrote:

> Hi Martin,
>
> What kind of FFLAGS do you have to specify for this inlining ?
>
> I am little bit concern that this will break some building
> where those S/R are not compiled (pkg not compiled,
> or our coupler in verification/cpl_aim+ocn/build_cpl
> with empty STANDARDDIRS, i.e., without model/src nor eesup/src)
>
> Jean-Michel
>
> On Tue, Sep 25, 2007 at 09:49:03PM +0200, Martin Losch wrote:
>> Hi there,
>>
>> for our SX8 I would like to include a list of routines to inlined in
>> the build_options file. Unfortunately that does not work with FFLAGS,
>> because then all the little tests in genmake2 look for the routines/
>> files to inlined and fail. I have included an extra variable
>> FEXTRAFLAGS into genmake2 that can contain such compiler options that
>> should not be used in the genmake2-tests. It is only used to actually
>> write the makefile: FFLAGS=${FFLAGS} ${FEXTRAFLAGS}. Is this OK to
>> check in? Or do we already have something like that and I just didn't
>> find it?
>>
>> Martin
>> _______________________________________________
>> MITgcm-devel mailing list
>> MITgcm-devel at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel