[Users] building on MIC
Steven R. Brandt
sbrandt at cct.lsu.edu
Fri Dec 14 09:12:30 CST 2012
I'm trying to build on MIC. In order to do that, I have to cross
compile. See attached cfg file.
Anyhow, I build with simfactory and get this:
End of options from '/home1/00044/tg457049/Cactus/configs/sim/OptionList'.
creating cache ./config.cache
checking host system type... x86_64-unknown-linux-gnu
checking whether make sets ${MAKE}... yes
checking whether the C compiler (mpicc -g3 -m128bit-long-double -mmic
-rdynamic -Wunused-variable ) works... yes
checking whether the C compiler (mpicc -g3 -m128bit-long-double -mmic
-rdynamic -Wunused-variable ) is a cross-compiler... yes
checking whether we are using GNU C... yes
checking whether the C++ compiler (mpicxx -g3 -m128bit-long-double -mmic
-std=c++03 -rdynamic -Wunused-variable ) works... yes
checking whether the C++ compiler (mpicxx -g3 -m128bit-long-double -mmic
-std=c++03 -rdynamic -Wunused-variable ) is a cross-compiler... yes
checking whether we are using GNU C++... yes
So I expect the mpicc compiler to be used. It isn't. What am I doing wrong?
Cheers,
Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: text/x-log
Size: 59323 bytes
Desc: not available
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20121214/d1d1e16d/attachment-0001.bin
-------------- next part --------------
# Fedora
#
# Yum install command line needed to make this work:
#
# yum -y install mpich2 mpich2-devel \
# gsl gsl-devel hdf5 hdf5-devel \
# gcc gcc-c++ gcc-gfortran patch \
# java-1.6.0-openjdk subversion \
# git openssl-devel
# Whenever this version string changes, the application is configured
# and rebuilt from scratch
VERSION = 2011-02-21
CPP = cpp
FPP = cpp
CC = mpicc
CXX = mpicxx
F77 = mpif77
F90 = mpif90
#CUCC = nvcc
#HOST_MACHINE=powerpc64-unknown-linux-gnu
CROSS_COMPILE=yes
ENDIAN=little
SIZEOF_LONG_LONG=8
SIZEOF_LONG_INT=8
SIZEOF_INT=4
SIZEOF_SHORT_INT=2
SIZEOF_LONG_DOUBLE=16
SIZEOF_DOUBLE=8
SIZEOF_FLOAT=4
SIZEOF_POINTER=8
#CUDA_ARCH = sm_20
#CUDA_DIR = /usr/local/cuda
#CUDA_LIBS = cuda cudart iberty
#CUDA_LIB_DIRS = /usr/local/cuda/lib64 /usr/lib64/nvidia /usr/lib64
CPPFLAGS =
FPPFLAGS =
# no -msse3
CFLAGS = -g3 -m128bit-long-double -mmic -rdynamic -Wunused-variable
CXXFLAGS = -g3 -m128bit-long-double -mmic -std=c++03 -rdynamic -Wunused-variable
F77FLAGS = -g3 -m128bit-long-double -mmic -fcray-pointer -ffixed-line-length-none
F90FLAGS = -g3 -m128bit-long-double -mmic -fcray-pointer -ffixed-line-length-none
LDFLAGS =
LIBDIRS =
C_LINE_DIRECTIVES = yes
F_LINE_DIRECTIVES = yes
# -check-uninit fails for asm output operands
DEBUG = no
CPP_DEBUG_FLAGS = -DCARPET_DEBUG
FPP_DEBUG_FLAGS = -DCARPET_DEBUG
C_DEBUG_FLAGS = -O0
CXX_DEBUG_FLAGS = -O0
F77_DEBUG_FLAGS = -O0 -ffixed-line-length-none
F90_DEBUG_FLAGS = -O0 -ffree-line-length-none
# On Abe, the options -O3, -xT, and -ip lead to segmentation faults
# near MPI calls
# With Intel 9, using -ip prevents debug information for local variables
# With Intel 9, using -O3 leads to very long compile times (> 45 minutes)
OPTIMISE = yes
CPP_OPTIMISE_FLAGS = -DKRANC_VECTORS # -DCARPET_OPTIMISE -DNDEBUG
FPP_OPTIMISE_FLAGS = # -DCARPET_OPTIMISE -DNDEBUG
C_OPTIMISE_FLAGS = -O2
CXX_OPTIMISE_FLAGS = -O2
F77_OPTIMISE_FLAGS = -O2
F90_OPTIMISE_FLAGS = -O2
PROFILE = no
CPP_PROFILE_FLAGS =
FPP_PROFILE_FLAGS =
C_PROFILE_FLAGS = -pg
CXX_PROFILE_FLAGS = -pg
F77_PROFILE_FLAGS = -pg
F90_PROFILE_FLAGS = -pg
OPENMP = no
CPP_OPENMP_FLAGS = -openmp
FPP_OPENMP_FLAGS = -D_OPENMP
C_OPENMP_FLAGS = -openmp
CXX_OPENMP_FLAGS = -openmp
F77_OPENMP_FLAGS = -openmp
F90_OPENMP_FLAGS = -openmp
WARN = yes
CPP_WARN_FLAGS =
FPP_WARN_FLAGS =
C_WARN_FLAGS =
CXX_WARN_FLAGS =
F77_WARN_FLAGS =
F90_WARN_FLAGS =
#MPI = CUSTOM
MPI_DIR = /opt/apps/intel13/impi/4.1.0.024/intel64
#MPI_INC_DIRS =
#MPI_LIB_DIRS =
#MPI_LIBS =
PTHREADS = yes
GSL_DIR=/usr
LIBJPEG_DIR=/usr
HDF5_DIR=/usr
ZLIB_DIR=/usr
More information about the Users
mailing list