[Answering an old mail from December.]
>>> "Braden" == Braden McDaniel <[EMAIL PROTECTED]> writes:
>>> "Markus" == Markus Werle <[EMAIL PROTECTED]> writes:
[...]
Markus> From somewhere behind the scenes automake/autoconf
Markus> decides to insert the following options to the compiler
Markus>
[...]
| 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/ma
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 Inte
On Fri, 2002-12-20 at 15:17, Alexandre Duret-Lutz wrote:
> >>> "Markus" == Markus Werle <[EMAIL PROTECTED]> writes:
>
> Markus> Hi!
> Markus> I have a problem with the latest autotools:
>
> Markus> From somewhere behind the scenes automake/autoconf
> Markus> decides to insert the following op
>>> "Markus" == Markus Werle <[EMAIL PROTECTED]> writes:
Markus> Hi!
Markus> I have a problem with the latest autotools:
Markus> From somewhere behind the scenes automake/autoconf
Markus> decides to insert the following options to the compiler
Markus> flags; -MT -MD -MP -MF
depcomp adds the
Hi!
I have a problem with the latest autotools:
>From somewhere behind the scenes automake/autoconf decides to insert
the following options to the compiler flags;
-MT -MD -MP -MF
these are not recognized, say ignored ith annoying warnings by
intel's C++ 7.0. Any idea how to remove these via
con