On Fri, 31 Oct 2008, matei wrote:

> James,
> I tried installing the new version, but all my scripts, including your
> primer my.script fail with a NAN at the march line.

> During the installation, everything seems to compile, but occasional
> conspicuous messages of things not working properly.  For example,
> when I run system check, i get:

> [matei@dexl SYSTEM]$ ./AMRITAsystem -check

> *********************************
> Testing: $AMRITA/SYSTEM/Linux/x86
> *********************************
> amrpp    OK
> AMRITA::system -- command failed!
> error near: end of line
> amrf77   OK
> amrcxx   OK
> amrar    OK
> amrld    OK
> AMRITA::system -- command failed!
> error near: end of line
> amrdu    OK
> amrtouch OK
> ***********************
> AMRITAsystem appears OK

> When you installed it on my guest account, did you run into any
> problems of this sort?  The only difference I could see is that the
> guest accound was set with tcsh and i'm currently working with bash.
> I have edited the appropriate paths, so i am not sure what the problem
> is.

> On Fri, 31 Oct 2008, matei wrote:

> > James,
> > I tried installing the new version, but all my scripts, including your
> > primer my.script fail with a NAN at the march line.

> > During the installation, everything seems to compile, but occasional
> > conspicuous messages of things not working properly.  For example,
> > when I run system check, i get:

> > [matei@dexl SYSTEM]$ ./AMRITAsystem -check

> Try running:

> /AMRITAsystem -verbose -check

> James

> > *********************************
> > Testing: $AMRITA/SYSTEM/Linux/x86
> > *********************************
> > amrpp    OK
> > AMRITA::system -- command failed!
> > error near: end of line
> > amrf77   OK
> > amrcxx   OK
> > amrar    OK
> > amrld    OK
> > AMRITA::system -- command failed!
> > error near: end of line
> > amrdu    OK
> > amrtouch OK
> > ***********************
> > AMRITAsystem appears OK

> > When you installed it on my guest account, did you run into any
> > problems of this sort?  The only difference I could see is that the
> > guest accound was set with tcsh and i'm currently working with bash.
> > I have edited the appropriate paths, so i am not sure what the problem
> > is.

On Fri, 31 Oct 2008, matei wrote:

> Funny thing, now there is no error message when running AMRITAsystem
> check and i all i did is go to lunch and come back ?!  cannot recall
> if i had logged out, but certainly have not re-compiled!

> nevertheless, the NAN persists with all scripts including my.script..

> matei

> > Try running:

> > ./AMRITAsystem -verbose -check

> > James

On Fri, 31 Oct 2008, matei wrote:

> When i type: > amrmake amrita

> the only sign of problem comes from:

> amrita flightcheck
> ******************
> CRITICAL   : missing ``gcc-g77|gcc-fortran''   : you can't compile
> plugin::{amrita,amr_sol}
> NONCRITICAL: missing ``ghostscript-x11''       : you can't use
> amrita::epsf2xxx
> NONCRITICAL: missing ``ghostscript-fonts-std'' : you can't use
> amrita::epsf2xxx
> NONCRITICAL: missing ``gpg''                   : you can't use amrpdf -
> signas -verify
> keeping record: $AMRITA/logs/target/serial/Linux/x86/O/src3p::perl

> ********************
> amrbuild src3p::perl
> ********************
> Sanity Checks
>    Filter::amrita OK!
>    Compress::Zlib OK!
>    Inline::       OK!
>    Inline::Python BROKEN!

>    Inline::Ruby   OK!
>    amrperl        OK!
> ********************************************************
> installed src3p::perl in: $AMRITA/bin/serial/Linux/x86/O

> Matei,

> Edit the file:

>    $AMRITA/SYSTEM/Linux/x86/amrf77.types

> and change the lines:

>    AMRLINT = INTEGER*4
>    SIZE_AMRLINT = 4

> to:

>    AMRLINE = INTEGER*8

>    SIZE_AMRLINT = 8

> then recompile using:

>    amrmake -force amrita

> The type AMRLINT is used for the mesh connectivity
> tables and was recently rejigged to allow for more
> mesh patches. For some reason, the above change
> which I hand edited on your machine did not find
> its way back into my master copy. Hence the problem
> you had with the new release. Note that the above
> didn't affect the tests I ran at my end as
> my machine uses Linux/x86_64 .

> James

> You mean:

> > Matei,

> > Edit the file:

> >    $AMRITA/SYSTEM/Linux/x86/amrf77.types

> > and change the lines:

> >    AMRLINT = INTEGER*4
> >    SIZE_AMRLINT = 4

> > to:

> >    AMRLINE = INTEGER*8

> AMRLINT=INTEGER*8
> right?

> >    SIZE_AMRLINT = 8

> > then recompile using:

> >    amrmake -force amrita

> > The type AMRLINT is used for the mesh connectivity
> > tables and was recently rejigged to allow for more
> > mesh patches. For some reason, the above change
> > which I hand edited on your machine did not find
> > its way back into my master copy. Hence the problem
> > you had with the new release. Note that the above
> > didn't affect the tests I ran at my end as
> > my machine uses Linux/x86_64 .

> > James

> You mean:

> >    AMRLINE = INTEGER*8
> AMRLINT=INTEGER*8
> right?