octave & intel C++

[John W. Eaton]

On 28-Feb-2008, Jaroslav Hajek wrote:

| hello,
| 
| I'm trying to compile recent snapshot of Octave's sources with Intel
| C++/Fortran (10.1) on an AMD Opteron machine.
| I've encountered the following problems:
| 1. --disable-picky-flags does not seem to work for configure. At
| least, -Wall -W -Wshadow are always appended to the flags,
| which causes icpc complain about the ambiguous -W.

The options controlled by --{en,dis}able-picky-flags are

  GCC_PICKY_FLAGS="-Wcast-align -Wcast-qual -Wmissing-prototypes \
    -Wpointer-arith -Wstrict-prototypes -Wwrite-strings"

  GXX_PICKY_FLAGS="-Wcast-align -Wcast-qual -Wpointer-arith \
    -Wwrite-strings -Weffc++ -Wenum-clash"

The other warning options that are enabled by default (-Wall, -W,
-Wshadow, and -Wold-style-cast) are only used if they appear to be
acceptable to the compiler.  See the OCTAVE_CC_FLAG and
OCTAVE_CXX_FLAG macros in aclocal.m4.  I'd certainly consider patches
to improve this macro.  Otherwise, if it is not working for you, you
can set EXTERN_CFLAGS and EXTERN_CXXFLAGS to override the defaults.

| 2. libcruft compiles successfully, but liboctave does not. The error
| occures on Array-C.cc, caused by instantiation of
| octave_sort<Complex>. The compiler gripes that it cannot find operator
| < (Complex, Complex).
| It works if #include <oct-sort.cc> is moved behind these operator
| declarations in Array-C.cc.
| (is this the way it should be fixed? If so, I'll make a changeset)

What do you mean by "behind"?

Please send a patch so we can see precisely what you are proposing.

Thanks,

jwe