On Tue, 29 Oct 2019, Matthew Knepley via petsc-users wrote:
> On Tue, Oct 29, 2019 at 2:35 PM Smith, Barry F. wrote:
>
> >
> >The problem is that this change DOES use the preprocessor on the f90
> > file, does it not? We need a rule that does not use the preprocessor.
> >
>
> This change ju
The problem is that this change DOES use the preprocessor on the f90 file,
does it not? We need a rule that does not use the preprocessor.
Barry
> On Oct 29, 2019, at 10:50 AM, Matthew Knepley via petsc-users
> wrote:
>
> On Tue, Oct 29, 2019 at 11:38 AM Randall Mackie wrote:
> Hi M
On Tue, 29 Oct 2019, Randall Mackie via petsc-users wrote:
> Dear PETSc users:
>
> In our code, we have one or two small .f90 files that are part of the
> software, and they have always compiled without any issues with previous
> versions of PETSc, using standard PETSc make files.
>
> However,
On Tue, Oct 29, 2019 at 10:54 AM Randall Mackie via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> Dear PETSc users:
>
> In our code, we have one or two small .f90 files that are part of the
> software, and they have always compiled without any issues with previous
> versions of PETSc, using stan
Dear PETSc users:
In our code, we have one or two small .f90 files that are part of the software,
and they have always compiled without any issues with previous versions of
PETSc, using standard PETSc make files.
However, starting with PETSc 3.12, they no longer compile.
Was there some reasons