[petsc-dev] [petsc-users] compiler related error (configuring Petsc)

Barry Smith barryfsmith at icloud.com
Tue Aug 1 14:21:30 CDT 2023

  Only four more years of this nonsense!

  One of the (now ancient) selling points of Unix was that it could be more nimble and evolve more rapidly than IBM's mainframe operating systems.


    Can't we have configure tell users explicitly the situation when they encounter this case and how to resolve it instead of needing constant email chatter for each individual Redhat user?

> On Aug 1, 2023, at 2:42 PM, Satish Balay via petsc-users <petsc-users at 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?

More information about the petsc-dev mailing list