[petsc-dev] [petsc-maint #54862] Compiler error with petsc-dev on PC

[Satish Balay]

ISGetBlock() is misleading. And we have ISBlockGetXXX functions.

Perhaps we should use ISBlockCheck()/ISStrideCheck().

Satish

On Fri, 22 Oct 2010, Barry Smith wrote:

> 
>   Stupid Fortran.
> 
>    I suggest changing to SGetBlock() and ISGetStride() since Get is common usage. Another alternative is ISIsStride() and ISIsBlock() but we don't commonly use IS so I would avoid introducing it.
> 
> 
>     Barry
> 
> 
> On Oct 21, 2010, at 4:29 AM, Satish Balay wrote:
> 
> > Ok - I think the following defs are cris-crossing and causing grief..
> > 
> > <petscis.h>
> > #define ISSTRIDE       "stride" /* ISType */
> > #define ISBLOCK        "block" /* ISType*/
> > 
> > <src/vec/is/impls/stride/ftn-auto/stridef.c>
> > #define isstride_ ISSTRIDE
> > void PETSC_STDCALL   isstride_(IS is,PetscBool  *flag, int *__ierr ){
> > 
> > <src/vec/is/impls/block/ftn-auto/blockf.c>
> > #define isblock_ ISBLOCK
> > void PETSC_STDCALL   isblock_(IS is,PetscBool  *flag, int *__ierr ){
> > 
> > Perhaps ISBlock(), ISStride() functions should be renamed?
> > 
> > Satish
> > 
> > On Thu, 21 Oct 2010, Hammond, Glenn wrote:
> > 
> >> Still the same errors.
> >> 
> >>> -----Original Message-----
> >>> From: Satish Balay [mailto:petsc-maint at mcs.anl.gov]
> >>> Sent: Wednesday, October 20, 2010 8:50 PM
> >>> To: petsc-maint at mcs.anl.gov; Hammond, Glenn
> >>> Subject: RE: [petsc-maint #54862] Compiler error with petsc-dev on PC
> >>> 
> >>> if configure is run - its is supporsed to regenerate
> >>> fortranstubs.. [and I see configure was run today]
> >>> 
> >>>>>>>> 
> >>> PETSc:
> >>>  File creation : Generated Fortran stubs
> >>> <<<<<
> >>> 
> >>> libfast in: /cygdrive/c/software/petsc-dev/src/vec/is/impls/stride/ftn-
> >>> auto
> >>> stridef.c^M
> >>> C:\software\PETSC-~4\src\vec\is\impls\stride\ftn-auto\stridef.c(60) :
> >>> error C2059: syntax error : 'string'^M
> >>> /usr/bin/ar: stridef.o: No such file or directory
> >>> libfast in: /cygdrive/c/software/petsc-dev/src/vec/is/impls/block
> >>> block.c^M
> >>> libfast in: /cygdrive/c/software/petsc-dev/src/vec/is/impls/block/ftn-
> >>> auto
> >>> blockf.c^M
> >>> C:\software\PETSC-~4\src\vec\is\impls\block\ftn-auto\blockf.c(78) :
> >>> error C2059: syntax error : 'string'^M
> >>> /usr/bin/ar: blockf.o: No such file or directory
> >>> 
> >>> <<<<<<
> >>> 
> >>>                Found a copy of SOWING in sowing-1.1.15
> >>> <<<<<<
> >>> 
> >>> Looks like you have an old sowing. I guess you need 'rm -rf PETSC_ARCH
> >>> externalpackages'
> >>> 
> >>> Satish
> >>> 
> >>> 
> >>> On Wed, 20 Oct 2010, Hammond, Glenn wrote:
> >>> 
> >>>> Of course not.  Didn't have to on my Linux box and Jaguar.  I will
> >>> try again.
> >>>> 
> >>>> Glenn
> >>>> 
> >>>> From: knepley at gmail.com [mailto:knepley at gmail.com] On Behalf Of
> >>> Matthew Knepley
> >>>> Sent: Wednesday, October 20, 2010 8:28 PM
> >>>> To: petsc-maint at mcs.anl.gov; Hammond, Glenn
> >>>> Subject: Re: [petsc-maint #54862] Compiler error with petsc-dev on PC
> >>>> 
> >>>> Did you 'make allfortranstubs'?
> >>>> 
> >>>>  Mat
> >>>> On Wed, Oct 20, 2010 at 10:25 PM, Hammond, Glenn
> >>> <glenn.hammond at pnl.gov<mailto:glenn.hammond at pnl.gov>> wrote:
> >>>> PETSc,
> >>>> 
> >>>> See attached logs.
> >>>> 
> >>>> Glenn
> >>>> 
> >>>> 
> >>>> 
> >>>> --
> >>>> What most experimenters take for granted before they begin their
> >>> experiments is infinitely more interesting than any results to which
> >>> their experiments lead.
> >>>> -- Norbert Wiener
> >>>> 
> >>>> 
> >> 
> >> 
> >> 
> > 
> > 
> 
> 
>