Re: configure and intel's C++: inappropriate flags -MT -MD -MP -MF

[Markus Werle]

Alexandre Duret-Lutz wrote:

> Maybe your are not setting the compiler early enough?  Since
> ./configure decides which flags to use it must know the
> compiler.  Therefore you should run
>
>   ./configure CC=mycc; make

This is what I did. So the problem is somewhere else.
The problem is that Intel's C++ _accepts_ these flags and
only emits a warning. This might confuse the autotools here:

[...]
make[1]: Entering directory `/work/tresca/markus/DORIS/doris-0.0.1'
if icpc -DHAVE_CONFIG_H -I. -I. -I.  -I. -I./src  -I/opt/boost-1.29.0 -I/work/tr
esca/markus/DIET   -ansi -MT TestPDEs.o -MD -MP -MF ".deps/TestPDEs.Tpo" \
  -c -o TestPDEs.o `test -f 'src/test/TestPDEs.C' || echo './'`src/test/TestPDEs
.C; \
then mv ".deps/TestPDEs.Tpo" ".deps/TestPDEs.Po"; \
else rm -f ".deps/TestPDEs.Tpo"; exit 1; \
fi
icpc: Command line warning: ignoring option '-M'; no argument required
icpc: Command line warning: ignoring option '-M'; no argument required
icpc: Command line warning: no action performed for specified object file(s)
icpc  -ansi   -o euler  TestPDEs.o SimpleRectangularStructured.o
make[1]: Leaving directory `/work/tresca/markus/DORIS/doris-0.0.1'


Markus