[petsc-dev] More CMake hatred
Jed Brown
jed at jedbrown.org
Thu Apr 5 22:44:03 CDT 2018
Matthew Knepley <knepley at gmail.com> writes:
> Error configuring EIGEN with cmake Could not execute "cd
> /projects/academic/knepley/PETSc3/petsc/arch-master-debug/externalpackages/eigen-eigen-5a0156e40feb/build
> && /projects/academic/knepley/PETSc3/petsc/arch-master-debug/bin/cmake ..
> -DCMAKE_INSTALL_PREFIX=/projects/academic/knepley/PETSc3/petsc/arch-master-debug
> -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_C_COMPILER="/user/knepley/bin/ccache
> mpicc" -DCMAKE_AR=/usr/bin/ar -DCMAKE_RANLIB=/usr/bin/ranlib
> -DCMAKE_C_FLAGS:STRING="-fPIC -fstack-protector -g3"
> -DCMAKE_C_FLAGS_DEBUG:STRING="-fPIC -fstack-protector -g3"
> -DCMAKE_C_FLAGS_RELEASE:STRING="-fPIC -fstack-protector -g3"
> -DCMAKE_CXX_COMPILER="/user/knepley/bin/ccache mpicxx"
> -DCMAKE_CXX_FLAGS:STRING="-fstack-protector -g -fPIC"
> -DCMAKE_CXX_FLAGS_DEBUG:STRING="-fstack-protector -g -fPIC"
> -DCMAKE_CXX_FLAGS_RELEASE:STRING="-fstack-protector -g -fPIC"
> -DCMAKE_Fortran_COMPILER="/user/knepley/bin/ccache mpif90"
> -DCMAKE_Fortran_FLAGS:STRING="-fPIC -ffree-line-length-0 -g"
> -DCMAKE_Fortran_FLAGS_DEBUG:STRING="-fPIC -ffree-line-length-0 -g"
> -DCMAKE_Fortran_FLAGS_RELEASE:STRING="-fPIC -ffree-line-length-0 -g"
> -DBUILD_SHARED_LIBS=on -DENABLE_OPENMP=OFF":
>
> -- The C compiler identification is unknown
>
> -- The CXX compiler identification is unknown
>
> -- Configuring incomplete, errors occurred!
>
> See also
> "/projects/academic/knepley/PETSc3/petsc/arch-master-debug/externalpackages/eigen-eigen-5a0156e40feb/build/CMakeFiles/CMakeOutput.log".
>
> See also
> "/projects/academic/knepley/PETSc3/petsc/arch-master-debug/externalpackages/eigen-eigen-5a0156e40feb/build/CMakeFiles/CMakeError.log".CMake
> Error at CMakeLists.txt:1 (project):
>
> The CMAKE_C_COMPILER:
>
>
> /user/knepley/bin/ccache mpicc
>
>
> is not a full path to an existing compiler tool.
>
>
> Tell CMake where to find the compiler by setting either the environment
>
> variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path
> to
>
> the compiler, or to the compiler name if it is in the PATH.
>
>
>
> CMake Error at CMakeLists.txt:1 (project):
>
> The CMAKE_CXX_COMPILER:
>
>
> /user/knepley/bin/ccache mpicxx
>
>
> is not a full path to an existing compiler tool.
>
>
> Tell CMake where to find the compiler by setting either the environment
>
> variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full
> path
>
> to the compiler, or to the compiler name if it is in the PATH.
>
>
>
> *******************************************************************************
>
>
> [knepley at rush:/projects/academic/knepley/PETSc3/petsc]$ which mpicc
>
> /util/common/openmpi/3.0.0/gcc-4.8.5/bin/mpicc
>
> [knepley at rush:/projects/academic/knepley/PETSc3/petsc]$ echo $PATH
>
> /util/common/openmpi/3.0.0/gcc-4.8.5/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/lpp/mmfs/bin:/opt/dell/srvadmin/bin:/user/knepley/bin
>
> I cannot see why it would say this.
It's complaining that the CC is two words instead of a single path. You
can make a link
ln -s `which ccache` ~/bin/mpicc
and then CC=$HOME/bin/mpicc will work. Yes, it's irritating.
> Matt
>
> --
> 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
>
> https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/>
More information about the petsc-dev
mailing list