On Wed, 25 Feb 2004, Tor Arntsen wrote:

> Yesterday I did a bunch of builds with different combinations of flags, here
> are some suggestions. NB: This is for ICC 8.0 (6.0 and older doesn't have
> the -Wall flag, although it does have -wd<n>. I don't know about icc 7.0 as
> I never used that version because of its license).

I'm adjusting the configure detection now to use -wd279 on all icc compilers,
and -Wall on everything above icc 6.0.

> "-Wall" makes it pretty chatty.

So I've seen! ;-) I take it we can use multiple -wd options if I we want to
disable some more warnings?

> I also found out about the -no-gcc flag, with this flag icc doesn't define
> the __GNUC__ flags, and thus isn't detected by autoconf as gcc. Using this
> flag I could do some builds testing the different options.

That's useful of course, but with my correct detection of icc, you can leave
it without -no-gcc and then the configure script will decide the proper level
for --enable-debug.

> I uploaded two builds so you can see for yourself, one with -no-gcc (which
> means that with the current autoconf no flags should be set), and another
> with -no-gcc -Wall -wd279.

Some of those are only annoying. Such as the remarks 981, 1418, 1419 and the
181 in most cases. In fact, all warnings on string (*printf) formats are
better switched off since they're so often wrong.

It does produce a number of interesting warnings on conversions from long to
ints.

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
   [[ Do not send mails to this email address. They won't reach me. ]]