<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Apr 5, 2018 at 11:44 PM, Jed Brown <span dir="ltr"><<a href="mailto:jed@jedbrown.org" target="_blank">jed@jedbrown.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> writes:<br>
<br>
> Error configuring EIGEN with cmake Could not execute "cd<br>
> /projects/academic/knepley/<wbr>PETSc3/petsc/arch-master-<wbr>debug/externalpackages/eigen-<wbr>eigen-5a0156e40feb/build<br>
> && /projects/academic/knepley/<wbr>PETSc3/petsc/arch-master-<wbr>debug/bin/cmake ..<br>
> -DCMAKE_INSTALL_PREFIX=/<wbr>projects/academic/knepley/<wbr>PETSc3/petsc/arch-master-debug<br>
> -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_C_COMPILER="/user/<wbr>knepley/bin/ccache<br>
> mpicc" -DCMAKE_AR=/usr/bin/ar -DCMAKE_RANLIB=/usr/bin/ranlib<br>
> -DCMAKE_C_FLAGS:STRING="-fPIC -fstack-protector -g3"<br>
> -DCMAKE_C_FLAGS_DEBUG:STRING="<wbr>-fPIC -fstack-protector -g3"<br>
> -DCMAKE_C_FLAGS_RELEASE:<wbr>STRING="-fPIC -fstack-protector -g3"<br>
> -DCMAKE_CXX_COMPILER="/user/<wbr>knepley/bin/ccache mpicxx"<br>
> -DCMAKE_CXX_FLAGS:STRING="-<wbr>fstack-protector -g -fPIC"<br>
> -DCMAKE_CXX_FLAGS_DEBUG:<wbr>STRING="-fstack-protector -g -fPIC"<br>
> -DCMAKE_CXX_FLAGS_RELEASE:<wbr>STRING="-fstack-protector -g -fPIC"<br>
> -DCMAKE_Fortran_COMPILER="/<wbr>user/knepley/bin/ccache mpif90"<br>
> -DCMAKE_Fortran_FLAGS:STRING="<wbr>-fPIC -ffree-line-length-0 -g"<br>
> -DCMAKE_Fortran_FLAGS_DEBUG:<wbr>STRING="-fPIC -ffree-line-length-0 -g"<br>
> -DCMAKE_Fortran_FLAGS_RELEASE:<wbr>STRING="-fPIC -ffree-line-length-0 -g"<br>
> -DBUILD_SHARED_LIBS=on -DENABLE_OPENMP=OFF":<br>
><br>
> -- The C compiler identification is unknown<br>
><br>
> -- The CXX compiler identification is unknown<br>
><br>
> -- Configuring incomplete, errors occurred!<br>
><br>
> See also<br>
> "/projects/academic/knepley/<wbr>PETSc3/petsc/arch-master-<wbr>debug/externalpackages/eigen-<wbr>eigen-5a0156e40feb/build/<wbr>CMakeFiles/CMakeOutput.log".<br>
><br>
> See also<br>
> "/projects/academic/knepley/<wbr>PETSc3/petsc/arch-master-<wbr>debug/externalpackages/eigen-<wbr>eigen-5a0156e40feb/build/<wbr>CMakeFiles/CMakeError.log".<wbr>CMake<br>
> Error at CMakeLists.txt:1 (project):<br>
><br>
>   The CMAKE_C_COMPILER:<br>
><br>
><br>
>     /user/knepley/bin/ccache mpicc<br>
><br>
><br>
>   is not a full path to an existing compiler tool.<br>
><br>
><br>
>   Tell CMake where to find the compiler by setting either the environment<br>
><br>
>   variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path<br>
> to<br>
><br>
>   the compiler, or to the compiler name if it is in the PATH.<br>
><br>
><br>
><br>
> CMake Error at CMakeLists.txt:1 (project):<br>
><br>
>   The CMAKE_CXX_COMPILER:<br>
><br>
><br>
>     /user/knepley/bin/ccache mpicxx<br>
><br>
><br>
>   is not a full path to an existing compiler tool.<br>
><br>
><br>
>   Tell CMake where to find the compiler by setting either the environment<br>
><br>
>   variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full<br>
> path<br>
><br>
>   to the compiler, or to the compiler name if it is in the PATH.<br>
><br>
><br>
><br>
> ******************************<wbr>******************************<wbr>*******************<br>
><br>
><br>
> [knepley@rush:/projects/<wbr>academic/knepley/PETSc3/petsc]<wbr>$ which mpicc<br>
><br>
> /util/common/openmpi/3.0.0/<wbr>gcc-4.8.5/bin/mpicc<br>
><br>
> [knepley@rush:/projects/<wbr>academic/knepley/PETSc3/petsc]<wbr>$ echo $PATH<br>
><br>
> /util/common/openmpi/3.0.0/<wbr>gcc-4.8.5/bin:/usr/lib64/qt-3.<wbr>3/bin:/usr/local/bin:/usr/bin:<wbr>/usr/local/sbin:/usr/sbin:/<wbr>usr/lpp/mmfs/bin:/opt/dell/<wbr>srvadmin/bin:/user/knepley/bin<br>
><br>
> I cannot see why it would say this.<br>
<br>
</div></div>It's complaining that the CC is two words instead of a single path.  You<br>
can make a link<br>
<br>
  ln -s `which ccache` ~/bin/mpicc<br>
<br>
and then CC=$HOME/bin/mpicc will work.  Yes, it's irritating.</blockquote><div><br></div><div>I found your answer on Stack Exchange</div><div><br></div><div>  <a href="https://stackoverflow.com/questions/1815688/how-to-use-ccache-with-cmake">https://stackoverflow.com/questions/1815688/how-to-use-ccache-with-cmake</a></div><div><br></div><div>This is definitely face punch territory.</div><div><br></div><div>   Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
>    Matt<br>
><br>
> --<br>
> What most experimenters take for granted before they begin their<br>
> experiments is infinitely more interesting than any results to which their<br>
> experiments lead.<br>
> -- Norbert Wiener<br>
><br>
</span>> <a href="https://www.cse.buffalo.edu/~knepley/" rel="noreferrer" target="_blank">https://www.cse.buffalo.edu/~<wbr>knepley/</a> <<a href="http://www.caam.rice.edu/~mk51/" rel="noreferrer" target="_blank">http://www.caam.rice.edu/~<wbr>mk51/</a>><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.caam.rice.edu/~mk51/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div>
</div></div>