TRIQS/TRIQS — Issue #14: Mpich on top of intel compiler build
Author: A32167
Created: 2011-11-25 12:48:33+00:00
State: open

Hi, everyone.
I'm trying to build triqs on top of intel compiler with mpich2.
The configure script is almost the same as in issue #9.

Here it is:

CXX="icpc" CC="icc" F77="ifort" F90="ifort" cmake \
-DBLAS_LIBRARY=-lmkl_core -DLAPACK_LIBRARY="-lgm;-lmkl_intel_lp64;-lmkl_sequential;-lpthread" \
-DCBLAS_INCLUDE_DIR=/usr/local/intel/composerxe/2011.7.256/mkl/include \
-DLAPACK_LINKER_FLAGS=-L/usr/local/intel/composerxe/2011.7.256/mkl/lib/intel64 \
-DBOOST_SOURCE_DIR=/home/antipov/code/boost_svn \
-DMPIEXEC:FILEPATH=/usr/local/mpich2-ch3/intel-fPIC/bin/bin/mpiexec \
-DMPI_COMPILER:FILEPATH=/usr/local/mpich2-ch3/intel-fPIC/bin/mpicxx \
-DMPI_LIBRARY:FILEPATH=/usr/local/mpich2-ch3/intel-fPIC/lib/libmpich.a \
-DMPI_INCLUDE_PATH:STRING=/usr/local/mpich2-ch3/intel-fPIC/include \
-DCMAKE_INSTALL_PREFIX=/home/antipov/_local \
/home/antipov/code/triqs

Here's what I receive:

Linking CXX executable a_x_ty_nopy
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `MPL_env2str'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `_intel_fast_memset'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `MPL_env2int'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `MPL_env2range'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `MPL_env2bool'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `__intel_sse2_strdup'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `__intel_sse2_strlen'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `__intel_sse2_strncmp'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `__intel_sse2_strchr'
../../../../foreignlibs/boost/libboost_for_triqs.so: undefined reference to `_intel_fast_memcpy'

MPL is some obsolete bindings of mpich and I guess calling them can be avoided by specifiying some options in cmake.

All the best,
Andrey.