Re: GCC & errors

Noted :]

I do have a question though: are we concerned about the MIPS fullwarn
flag? If we are, pedantic seems appropriate... As I suspect fullwarn
~ -pedantic

Rob

----- Original Message -----
From: "Henrik Nordstrom" <hno@hem.passagen.se>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <squid-dev@squid-cache.org>
Sent: Friday, March 09, 2001 9:11 PM
Subject: Re: GCC & errors

> Note: I said -Werror, not -W
>
> -Werror makes GCC threat warnings as errors, making sure the compile
> stops when there is a warning.
>
> /Henrik
>
>
> Robert Collins wrote:
> >
> > Well -Wall turns on most errors.
> > I actuall find -pedantic turns on less errors that
> > -Wall -W
> > which was realllllly pedantic.
> >
> > Still, up to the individual :]
> >
> > the following link is useful for reference purposes..
> > http://gcc.gnu.org/onlinedocs/gcc_3.html#SEC10
> >
> > Rob
> >
> > ----- Original Message -----
> > From: "Henrik Nordstrom" <hno@hem.passagen.se>
> > To: "Robert Collins" <robert.collins@itdomain.com.au>
> > Cc: <squid-dev@squid-cache.org>
> > Sent: Friday, March 09, 2001 10:14 AM
> > Subject: Re: GCC & errors
> >
> > > -pedantic gives a bit too many errors, but there are quite many
> > warning
> > > flags that can be enabled in GCC. I strongly recommend at least
using
> > > -Werror to not accidently overlook one warning..
> > >
> > > /Henrik
> > >
> > >
> > > Robert Collins wrote:
> > > >
> > > > can I suggest that developers test their code building
> > with -pedantic
> > > > (ie in the Makefile
> > > > AC_CFLAGS = -g -O2 -Wall -pedantic
> > > > )
> > > >
> > > > or
> > > > CFLAGS = '-g -O2 -Wall -pedantic' ../srctree/configure ....
> > > >
> > > > That has got me at least some of the errors Adrian is seeing
with
> > irix
> > > > (different report format, same error AFAICT)
> > > >
> > > > Rob
> > >
>
>
Received on Fri Mar 09 2001 - 03:50:34 MST