Right, so configure did the proper job and told you that your compiler does not (fully) work with C++11, there is no point in trying to add extra flags to bypass this limitation. As Satish suggested: either use a newer g++ or configure --with-cxx=0
Thanks, Pierre > On 2 Aug 2023, at 6:42 AM, maitri ksh <maitri....@gmail.com> wrote: > > sure, attached. > > On Tue, Aug 1, 2023 at 10:36 PM Jacob Faibussowitsch <jacob....@gmail.com > <mailto:jacob....@gmail.com>> wrote: >> >> Initially I got an error related >> >> to 'C++11' flag, >> >> Can you send the configure.log for this as well >> >> Best regards, >> >> Jacob Faibussowitsch >> (Jacob Fai - booss - oh - vitch) >> >> > On Aug 1, 2023, at 14:42, Satish Balay via petsc-users >> > <petsc-users@mcs.anl.gov <mailto:petsc-users@mcs.anl.gov>> wrote: >> > >> >> gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44) >> > >> > Is it possible for you to use a newer version GNU compilers? >> > >> > If not - your alternative is to build PETSc with --with-cxx=0 option >> > >> > But then - you can't use --download-superlu_dist or any pkgs that need >> > c++ [you could try building them separately though] >> > >> > Satish >> > >> > >> > On Tue, 1 Aug 2023, maitri ksh wrote: >> > >> >> I am trying to compile petsc on a cluster ( x86_64-redhat-linux, ' >> >> *configure.log'* is attached herewith) . Initially I got an error related >> >> to 'C++11' flag, to troubleshoot this issue, I used 'CPPFLAGS' and >> >> 'CXXFLAGS' and could surpass the non-compliant error related to c++ >> >> compiler >> >> but now it gives me another error 'cannot find a C preprocessor'. How to >> >> fix this? >> >> >> > >> > <configure.log>
