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

[Alexandre Duret-Lutz]

[...]

| The problem is that Intel's C++ _accepts_ these flags and
| only emits a warning. This might confuse the autotools here:

Yep.

| 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'

What does .deps/TestPDEs.Po contains after this?  Do you
understand which -Mx options this diagnotic is referring to
(there is only two warnings, but four -Mx options).  How does
icpc's -M option work?  Are these warnings output to stdout or
stderr?  Is there any icpc-specific environment variable that can
be set to turn warnings into errors?
-- 
Alexandre Duret-Lutz