[petsc-users] cmake METIS problem

[Gong Ding]

No, petsc filters all the FC, CC and CXX env variable and gives a warning.
p { margin: 0; }You can set the CXX environment variable, CMake should always pick those up.
Tim
From:"Gong Ding" <gdiso at ustc.edu>
To:"PETSc users list" <petsc-users at mcs.anl.gov>
Sent:Monday, December 5, 2011 7:58:29 AM
Subject:Re: [petsc-users] cmake METIS problem
I do specify --with-cc --with-cxx --with-fc. Here is the configure options
configure --known-level1-dcache-size=32768 --known-level1-dcache-linesize=32 --known-level1-dcache-assoc=2 --known-memcmp-ok=1 --known-endian=big --known-sizeof-char=1 --known-sizeof-void-p=8 --known-sizeof-short=2 --known-sizeof-int=4 --known-sizeof-long=8 --known-sizeof-long-long=8 --known-sizeof-float=4 --known-sizeof-double=8 --known-sizeof-size_t=8 --known-bits-per-byte=8 --known-sizeof-MPI_Comm=4 --known-sizeof-MPI_Fint=4 --known-mpi-long-double=1 --download-f-blas-lapack=1 --download-mumps=1 --download-blacs=1 --download-metis=1  --download-parmetis=1 --download-scalapack=1 --download-superlu=1 --download-superlu_dist=1 --with-c2html=0  --with-debugging=0 --with-clanguage=cxx --with-cc="mpcc_r" --with-fc="mpxlf_r" --with-cxx="mpCC_r" --CFLAGS="-q64 -O3 -qmaxmem=-1 -qstrict -qarch=auto -qtune=auto" --CXXFLAGS="-q64 -O3 -qmaxmem=-1 -qipa -qstrict -qarch=auto -qtune=auto" --FFLAGS="-q64 -O3 -qmaxmem=-1 -qarch=auto -qtune=auto" --with-sowing=0  --with-batch=1 --with-shared-libraries=1 --known-mpi-shared-libraries=1 --with-x=0 --with-pic=1
But cmake does not use given cxx. You see, cc="mpcc_r" is passed to cmake, but no cxx.
Cmake tries to find cxx but failed.
 
 Hi,
 I try to install petsc-dev on AIX/PPC cluster.
 I'd like to use xlc, however, there is a dead gcc/g++ installed in /usr/bin.
 Since I am not the administrator, I can't do anything to remove/update it.
Specify the compilers using --with-cc --with-cxx --with-fc. I suggest you specify the MPIcompiler wrappers for this machine.
   Matt  The cmake configure file for metis tries to find c++ compiler, and reported error with that g++.
 Error running configure on METIS: Could not execute "cd /gpfs1/cogenda/cogenda/packages/petsc-dev/externalpackages/metis-5.0.2 && make distclean && make config prefix=/gpfs1/cogenda/cogenda/packages/petsc-dev/IBM-XLCPP cc="mpcc_r" doubleprecision=1":
 rm -rf build/AIX-000092FAD400
 rm -rf build/AIX-000092FAD400
 mkdir -p build/AIX-000092FAD400
 cd build/AIX-000092FAD400 && cmake /gpfs1/cogenda/cogenda/packages/petsc-dev/externalpackages/metis-5.0.2 -DCMAKE_VERBOSE_MAKEFILE=1 -DGKLIB_PATH= -DCMAKE_INSTALL_PREFIX=/gpfs1/cogenda/cogenda/packages/petsc-dev/IBM-XLCPP -DCMAKE_C_COMPILER=mpcc_r -DMETIS_USE_DOUBLEPRECISION=1
 -- The C compiler identification is XL
 -- The CXX compiler identification is unknown
 -- Check for working C compiler: /usr/bin/mpcc_r
 -- Check for working C compiler: /usr/bin/mpcc_r -- works
 -- Detecting C compiler ABI info
 -- Detecting C compiler ABI info - done
 -- Check for working CXX compiler: /usr/bin/g++
 -- Check for working CXX compiler: /usr/bin/g++ -- broken
 -- Configuring incomplete, errors occurred!
 I think the testing for c++ compiler can be removed here?
--
What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
 -- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20111205/6a0dd5ac/attachment.htm>