[petsc-dev] gcc 10

[Satish Balay]

The c++ thingy is on a centos-7 box - i.e with gcc-4.8.5 as the system compiler.

However the build was with [a manually built] clang-6.0 - which for some
reason is using the includes from this system gcc.

Satish

On Mon, 13 Jul 2020, Jed Brown wrote:

> I don't know what failure you're referring to.  The C++ complex thing might have been a matter of the antique compiler.
> 
> Matthew Knepley <knepley at gmail.com> writes:
> 
> > Why did Mark have the gcc 10 failure on our example. Was it something with
> > did in it?
> >
> >    Matt
> >
> > On Mon, Jul 13, 2020 at 12:43 PM Jed Brown <jed at jedbrown.org> wrote:
> >
> >> You want this for PETSc or for external packages?  We add it for a bunch
> >> of external packages.  I've been building PETSc with gcc/gfortran-10 for
> >> months now.
> >>
> >> Matthew Knepley <knepley at gmail.com> writes:
> >>
> >> > Do we have gfortran from gcc 10 running anywhere? We need a check to
> >> enable
> >> >
> >> >   -fallow-argument-mismatch
> >> >
> >> > from configure. Should be as simple as compiling Fortran which has
> >> > PetscObjectSetName() in it.
> >> >
> >> >   Thanks,
> >> >
> >> >       Matt
> >> >
> >> > --
> >> > 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
> >> >
> >> > https://www.cse.buffalo.edu/~knepley/ <
> >> http://www.cse.buffalo.edu/~knepley/>
> >>
> >
> >
> > -- 
> > 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
> >
> > https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
>