[petsc-dev] gcc 10
Barry Smith
bsmith at petsc.dev
Mon Jul 13 12:44:36 CDT 2020
The C++ complex thing and the gfortran thing are totally unrelated except they both come from Mark and involve the Gnu community.
> On Jul 13, 2020, at 12:40 PM, Jed Brown <jed at jedbrown.org> 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/>
More information about the petsc-dev
mailing list