[MITgcm-support] (no subject)

[fancer fancer]

Hi, q Li

I don't use mpif77, but I compile with gfortran. I take the following
output of libraries checking:

===  Checking system libraries  ===
  Do we have the system() command using gfortran...  yes
  Do we have the fdate() command using gfortran...  yes
*  Do we have the etime() command using gfortran...  no*
  Can we call simple C routines (here, "cloc()") using gfortran...  yes
  Can we unlimit the stack size using gfortran...  yes
  Can we register a signal handler using gfortran...  yes
  Can we use stat() through C calls...  yes
  Can we create NetCDF-enabled binaries...  yes

Absence of etime()'s maintenance doesn't interfere with my simulations at
all. To tell the truth I never paid my attention on this output.
It you try to find all calls of the etime() (ETIME()) function You'll see,
that it isn't used in the model/ and pkg/ sources. Therefore in my opinion
absence of the etime() function is not so critical.
But the comprehensive answer about why it is checked here I would hear too.

Suncerely,
Serge V. Semin

On Tue, Mar 20, 2012 at 2:38 AM, q li <qliuri at yahoo.com> wrote:

> Hi,
>
> When I genmake2 the codes on a cluster, I got this feedback, although I
> still can compile and run the model and the output also seems all right.
>
> ===  Checking system libraries  ===
>   Do we have the system() command using mpif77...  yes
>   Do we have the fdate() command using mpif77...  yes
>   Do we have the etime() command using mpif77...  no
>   Can we call simple C routines (here, "cloc()") using mpif77...  yes
>   Can we unlimit the stack size using mpif77...  yes
>   Can we register a signal handler using mpif77...  yes
>   Can we use stat() through C calls...  yes
>   Can we create NetCDF-enabled binaries...  no
>
> Anyone knows how to make etime() to "yes"? Will this interfere with my
> simulation?
>
> Best regards,
>
> Li
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20120320/ac0d20a5/attachment.htm>