Compiled information for Petsc 2.3.2-p10

[Barry Smith]

  Strange, never seen that before. It is likely you can just ignore
it.

   Barry




On Tue, 9 Oct 2007, Trivedi, Jagruti CIV 470000D, 474300D wrote:

>  
> Hello Licendro,
> 
> Here is the first question after the installation of petsc-2.3.3-p6.
> 
> I ran:
> Config/config.py --with-cc=gcc --with-fc=g77 --download-f-blas-lapack=1 --download-mpich=1
> 
> /usr/local/bin/make all test /* run gnu make
> 
> I get the following status error:
> 
> Running test examples to verify correct installation
> c/C++ example src/snes/examples/tutorials/ex19 run successfully with 1 MPI process
> 
> c/C++ example src/snes/examples/tutorials/ex19 run successfully with 2 MPI process
> 
> Graphics example src/snes/examples/tutorials/ex19 run successfully with 1 MPI process
> 
> /bin/sh: test: argument expected
>  make[3]: [ex19.rm] Error 1 (ignored)
> /bin/sh: test: argument expected
>  make[3]: [ex19.rm] Error 1 (ignored)
> /bin/sh: test: argument expected
>  make[3]: [ex19.rm] Error 1 (ignored)
> /bin/sh: test: argument expected
>  make[3]: [ex19.rm] Error 1 (ignored)
> Fortran example src/snes/examples/tutorials/ex5f run successfully with 1 MPI process
> /bin/sh: test: argument expected
>  make[3]: [ex5f.rm] Error 1 (ignored)
> /bin/sh: test: argument expected
>  make[3]: [ex5f.rm] Error 1 (ignored)
> /bin/sh: test: argument expected
>  make[3]: [ex5f.rm] Error 1 (ignored)
> /bin/sh: test: argument expected
>  make[3]: [ex5f.rm] Error 1 (ignored)
> Completed test examples
> 
> Is this the correct installation? Why am I getting this error messages?
> 
> Thanks,
> 
> ....Jagruti
> 
> -----Original Message-----
> From: owner-petsc-users at mcs.anl.gov [mailto:owner-petsc-users at mcs.anl.gov] On Behalf Of Lisandro Dalcin
> Sent: Tuesday, October 09, 2007 12:31
> To: petsc-users at mcs.anl.gov
> Subject: Re: Compiled information for Petsc 2.3.2-p10
> 
> I want to suggest you to update to 2.3.3. Of course, you have the extra trouble of figuring out yourself the cummulative changes since 2.2.1.
> 
> Go ahead updating to 2.3.3, and I can help you at any point you have trouble.
> 
> 
> 
> On 10/9/07, Trivedi, Jagruti CIV 470000D, 474300D <jagruti.trivedi at navy.mil> wrote:
> >
> > Do you mean that I should apply changes from 2.2.1 to 2.3.0 and then
> > 2.3.1 and so forth until I come upto 2.3.3 version or I can apply 
> > directly from 2.2.1 to 2.3.3?
> >
> > ...Jagruti
> > -----Original Message-----
> > From: owner-petsc-users at mcs.anl.gov
> > [mailto:owner-petsc-users at mcs.anl.gov] On Behalf Of Satish Balay
> > Sent: Tuesday, October 09, 2007 11:29
> > To: petsc-users at mcs.anl.gov
> > Subject: Re: Compiled information for Petsc 2.3.2-p10
> >
> >
> > It is possible that we didn't document all the changes between releases.
> >
> > But the recommended approach is to look at changes file for each 
> > version after 2.2.1 - and apply these changes.
> >
> > And if your code is in C - then the compiler will help in finding any 
> > undocumented changes in prototypes.. etc..
> >
> > BTW: the current release version is 2.3.3 [so you might want to 
> > upgrade to this version instead of 2.3.2]
> >
> > Satish
> >
> > On Tue, 9 Oct 2007, Trivedi, Jagruti CIV 470000D, 474300D wrote:
> >
> > >
> > >
> > > Hello there,
> > >
> > > I am trying to port my application from petsc 2.2.1 to petsc
> > 2.3.2-p10.
> > > Has anybody compiled
> > > The real life changes needed to make other than listed in the 
> > > changes file?
> > >
> > > I really appreciate if you have hands on do's and don'ts for porting 
> > > from petsc-2.2.1 to Petsc 2.3.2-p10.
> > >
> > > Looking forward to positive replies.
> > >
> > > Thanks and Best Regards,
> > >
> > > ....Jagruti
> > >
> > > NAWC
> > >
> >
> >
> 
> 
> --
> Lisandro Dalcín
> ---------------
> Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina
> Tel/Fax: +54-(0)342-451.1594
> 
>