"Smith, Barry F." writes:
> From below it looks like OpenMPI handles many compilers that
> don't handle type(*) by using some horrible non-portable
> pragmas? I can't say it excites me to want to add all the crap
> to PETSc configure/source.
>
>
Jed,
Thanks for checking this.
Satish,
Can you please upgrade the admittedly ancient compilers? Maybe this will
help for some compilers.
From below it looks like OpenMPI handles many compilers that don't handle
type(*) by using some horrible non-portable pragmas? I
"Smith, Barry F." writes:
>> On Oct 26, 2017, at 7:55 AM, Jed Brown wrote:
>>
>> Which compilers don't work?
>
>Your time is no more valuable than anyone else's. You can see the failed
> red lines at
>
>
> On Oct 26, 2017, at 7:55 AM, Jed Brown wrote:
>
> Which compilers don't work?
Your time is no more valuable than anyone else's. You can see the failed red
lines at
ftp://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/10/29/next.html
and click through to see the
Which compilers don't work?
"Smith, Barry F." writes:
>Jed,
>
> Unfortunately multiple fortran compilers we use do not support type(*) so
> we either configure check this stuff (annoying) or stop supporting lots of
> Fortran compilers.
>
>Satish,
>
>I
Jed,
Unfortunately multiple fortran compilers we use do not support type(*) so
we either configure check this stuff (annoying) or stop supporting lots of
Fortran compilers.
Satish,
I guess you need to check all the failed Fortran compilers and see if
they have versions that