[petsc-users] configure cannot find a c preprocessor

[Satish Balay]

>>>
Executing: mpicc -E  -I/dev/shm/pbs.3111462.hpc-pbs/petsc-fdYfuH/config.setCompilers  /dev/shm/pbs.3111462.hpc-pbs/petsc-fdYfuH/config.setCompilers/conftest.c
stderr:
gcc: warning: /usr/lib64/libcpuset.so.1: linker input file unused because linking not done
gcc: warning: /usr/lib64/libbitmask.so.1: linker input file unused because linking not done
<<<<

Looks like your mpicc is printing this verbose thing on stdout [why is
it doing a link check during preprocesing?] - thus confusing PETSc
configure.

Workarround is to fix this compiler not to print such messages. Or use different compilers..

What do you have for:

mpicc -show


Satish

On Wed, 20 Dec 2017, Santiago Andres Triana wrote:

> Dear petsc-users,
> 
> I'm trying to install petsc in a cluster using SGI's MPT. The mpicc
> compiler is in the search path. The configure command is:
> 
> ./configure --with-scalar-type=complex --with-mumps=1 --download-mumps
> --download-parmetis --download-metis --download-scalapack
> 
> However, this leads to an error (configure.log attached):
> 
> ===============================================================================
>              Configuring PETSc to compile on your system
> 
> ===============================================================================
> TESTING: checkCPreprocessor from
> config.setCompilers(config/BuildSystem/config/setCompilers.py:599)
> 
> *******************************************************************************
>          UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
> details):
> -------------------------------------------------------------------------------
> Cannot find a C preprocessor
> *******************************************************************************
> 
> The configure.log says something about cpp32, here's the excerpt:
> 
> Possible ERROR while running preprocessor: exit code 256
> stderr:
> gcc: error: cpp32: No such file or directory
> 
> 
> Any ideas of what is going wrong? any help or comments are highly
> appreciated. Thanks in advance!
> 
> Andres
>