Sorry for the mistake. Please find the attached file.

On Thu, Aug 31, 2023 at 7:58 PM John Peterson <jwpeter...@gmail.com> wrote:

> Hi,
>
> The config.log that you sent this time does not seem to be related to the
> previous one, but rather to a MOOSE build? And the version of PETSc is
> totally different from the previous log, it is now PETSc 3.11.4.
>
> In any event, the relevant configure output is:
>
> configure:34458: checking for
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt//include/petscversion.h
>> configure:34458: result: yes
>> configure:34525: result: <<< Found PETSc 3.11.4 installation in
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt ... >>>
>> configure:34535: checking whether we can compile a trivial PETSc program
>> configure:34564: mpicxx -c  -std=gnu++11
>> -I/opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include
>> -I/opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt//include
>> -I/opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include
>> -I/opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include  conftest.cpp >&5
>> In file included from
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscsys.h:14:0,
>>                  from
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscbag.h:4,
>>                  from
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petsc.h:5,
>>                  from conftest.cpp:144:
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscconf.h:85:36:
>> error: expected '}' before '__attribute'
>>  #define PETSC_DEPRECATED_ENUM(why) __attribute((deprecated))
>>                                     ^
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscksp.h:430:76:
>> note: in expansion of macro 'PETSC_DEPRECATED_ENUM'
>>  #define KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED
>> KSP_DIVERGED_PCSETUP_FAILED PETSC_DEPRECATED_ENUM("Use
>> KSP_DIVERGED_PC_FAILED (since v3.11)")
>>
>>   ^
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscksp.h:452:15:
>> note: in expansion of macro 'KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED'
>>                KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED  = -11,
>>                ^
>> In file included from
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscsnes.h:6:0,
>>                  from
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscts.h:7,
>>                  from
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petsc.h:29,
>>                  from conftest.cpp:144:
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscksp.h:452:55:
>> error: expected unqualified-id before '=' token
>>                KSP_DIVERGED_PCSETUP_FAILED_DEPRECATED  = -11,
>>                                                        ^
>> /opt/moose/petsc-3.11.4/mpich-3.3_gcc-9.2.0-opt/include/petscksp.h:454:52:
>> error: expected declaration before '}' token
>>                KSP_CONVERGED_ITERATING          =  0} KSPConvergedReason;
>>                                                     ^
>
>
> So there is a syntax error related to the __attribute keyword that appears
> in one of the PETSc header files. This means that the compiler you are
> using:
>
> configure:5255: mpicc --version >&5
>> gcc (Homebrew GCC 5.5.0_7) 5.5.0
>
>
>
> is also different from the one in your previous email, and is apparently
> too old to be able to compile the version of PETSc you are using. Note that
> PETSc 3.11.4 is from March 2019 while GCC 5.5 is from 2017, so this could
> explain the discrepancy. These types of errors are pretty common when
> trying to build old versions of software from source on newer (looks like
> you are using Ubuntu 18.04) machines, so I would recommend using
> contemporary versions of all software.
>
> --
> John
>

-- 
**Disclaimer:*
This message was sent from Vellore Institute of Technology.  
The contents of this email may contain legally protected confidential or 
privileged information of “Vellore Institute of Technology”.  If you are 
not the intended recipient, you should not disseminate, distribute or copy 
this e-mail. Please notify the sender immediately and destroy all copies of 
this message and any attachments. If you have received this email in error, 
please promptly notify the sender by reply email and delete the original 
email and any backup copies without reading them.*

_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to