|
From: | RUSS BRENNAN |
Subject: | RE: Compiling Octave 3.2.3 with icpc 10.1 fails: more than one instance of overloaded function "octave_int_cmp_op::mop" |
Date: | Wed, 18 Aug 2010 11:54:02 -0500 |
I'm using 10.1.022, but I will see what happens if I upgrade. > Date: Wed, 18 Aug 2010 08:27:36 +0200 > Subject: Re: Compiling Octave 3.2.3 with icpc 10.1 fails: more than one instance of overloaded function "octave_int_cmp_op::mop" > From: address@hidden > To: address@hidden > CC: address@hidden > > On Mon, Aug 16, 2010 at 10:43 PM, RUSS BRENNAN <address@hidden> wrote: > > I am compiling from source using icc/icpc/mkl 10.1 on a CentOS 4.8 install. > > After lurking here a while and drudging through some issues, I get the > > following compile time error: > > > > icpc -c -I/usr/local/include/ -I/usr/local/include -I/usr/include/freetype2 > > -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc -DHAVE_CONFIG_H > > -mieee-fp -w -O2 -xW -mieee-fp -I/usr/local/include/ > > -I/usr/include/freetype2 int64NDArray.cc -o pic/int64NDArray.o > > oct-inttypes.h(1052): error: more than one instance of overloaded function > > "octave_int_cmp_op::mop" matches the argument list: > > function template "bool octave_int_cmp_op::mop<xop,T>(T, > > double)" > > function template "bool > > octave_int_cmp_op::mop<xop>(int64_t={long long}, double)" > > argument types are: (int64_t, const double) > > OCTAVE_INT_DOUBLE_CMP_OP (!=, ne) > > ^ > > detected during: > > instantiation of "bool operator!=(const octave_int<T> &, const > > double &) [with T=int64_t={long long}]" at line 57 of "intNDArray.cc" > > instantiation of "bool > > intNDArray<T>::any_element_not_one_or_zero() const [with T=octave_int64]" at > > line 32 of "int64NDArray.cc" > > > > compilation aborted for int64NDArray.cc (code 2) > > > > > > > > My configure line looks like this: > > ./configure --enable-shared --disable-static > > --with-blas='-L$MKLPATH -lmkl -lpthread' > > --with-lapack='-lmkl_lapack' > > LIBS="-L$MKLPATH $MKLPATH/libmkl_solver.a -Wl,--start-group -lm -lmkl_intel > > -lmkl_intel_thread -lmkl_core -Wl,--end-group -liomp5 -lpthread" > > --disable-extra-warning-flags > > F77=ifort FFLAGS="-O3 -xW" > > CC=icc CFLAGS="-O2 -xW -mieee-fp -I/usr/local/include/" > > CXX=icpc CXXFLAGS="-w -O2 -xW -mieee-fp -I/usr/local/include/" > > CPP="icc -E" CPPFLAGS="-I$MKLROOT/include/fftw -I/usr/local/include/" > > CXXPP="icpc -E" > > LDFLAGS=-L/usr/local/lib/ > > > > Broke it up for clarity. Any idea as to why I get this error? > > > > IIRC this is a bug in Intel C++ that has been subsequently fixed. > What's your exact Intel C++ version? It's fixed in 11.0.074, but I > think it was already fixed in 10.1.008. > > > > Another thing to ponder, how can I make octave recognize intel's fftw > > implementation? > > No idea, but if the interface is compatible, Octave can't really tell > the difference. > > -- > RNDr. Jaroslav Hajek, PhD > computing expert & GNU Octave developer > Aeronautical Research and Test Institute (VZLU) > Prague, Czech Republic > url: www.highegg.matfyz.cz |
[Prev in Thread] | Current Thread | [Next in Thread] |