[petsc-users] PETSc 3.2 release candidate

[Tabrez Ali]

Thanks! FCPPFLAGS did it.

On 09/03/2011 01:03 PM, Satish Balay wrote:
> You can try FCPPFLAGS instead of PETSC_INCLUDE
>
> Also - suggest renaming all sources [that call PESc] to .F90 - and
> simplify makefile. [as PETSc targets compile .F90 files properly.]
>
> Satish
>
> On Sat, 3 Sep 2011, Tabrez Ali wrote:
>
>> Hello
>>
>> What is the equivalent of $(PETSC_INCLUDE) in petsc-3.2? I am using Fortran
>> and my files end in .f90. My working Makefile for petsc-3.1 (with gfortran)
>> looks like
>>
>> include ${PETSC_DIR}/conf/variables
>> include ${PETSC_DIR}/conf/rules
>> all:
>>          mpif90 -c -Wall -x f95-cpp-input $(PETSC_INCLUDE) a.f90 b.f90 c.f90
>>          $(FLINKER) a.o b.o c.o $(PETSC_FORTRAN_LIB) $(PETSC_LIB) -o exec
>>          $(RM) *.o *.mod
>>
>> With 3.2 I get the error
>>
>> stali at i5:~/src$ make all
>> mpif90 -c -Wall -x f95-cpp-input a.f90 b.f90 c.f90
>> b.f90:8:0: fatal error: finclude/petscsys.h: No such file or directory
>>
>> Thanks in advance
>>
>> Tabrez
>>
>> On 09/02/2011 09:01 PM, Satish Balay wrote:
>>> Also one can use the following tarball. It will correspond to
>>> petsc-3.2 sources for the next few days. And i've set it up to be
>>> updated every 3 hours [from the sources in mercurial].
>>>
>>> http://ftp.mcs.anl.gov/pub/petsc/petsc-dev.tar.gz
>>>
>>> Satish
>>>
>>> On Fri, 2 Sep 2011, Barry Smith wrote:
>>>
>>>>      You can find the PETSc 3.2 release candidate via Mecurial at:
>>>>> ssh://petsc@petsc.cs.iit.edu//hg/petsc/releases/petsc-3.2
>>>>> or    http://petsc.cs.iit.edu/petsc/releases/petsc-3.2
>>>>> ssh://petsc@petsc.cs.iit.edu//hg/petsc/releases/BuildSystem-3.2
>>>>> or    http://petsc.cs.iit.edu/petsc/releases/BuildSystem-3.2
>>>>      If you find any problems please let us know.  We'll be making the
>>>> tarball in a couple of days.
>>>>
>>>>      Thanks
>>>>
>>>>       Barry
>>>>
>>>>      If you fix anything, please make the fix in petsc-3.2 not petsc-dev
>>>>
>>>>
>>