Wireshark-dev: Re: [Wireshark-dev] Prevent compiler warnings by using "stop on warnings"/"treat
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Wed, 21 Mar 2007 08:32:26 +0100
On Wed, Mar 21, 2007 at 08:29:45AM +0100, Joerg Mayer wrote:
> On Tue, Mar 20, 2007 at 11:09:40PM -0700, Stephen Fisher wrote:
> > Thanks.  I introduced -Werror into the configure.in file in wiretap/ 
> > locally to follow Ulf's lead on the Win32 side and it broke the glib 
> > test program.  The glib test program compiles with warnings (turned 
> > errors)!  Something to look into...
> 
> Glib and glib2 have some warnings that cannot be avoided, like declaring
> a function() instead of funktion(types). At least in one place there is
> even a comment that explains why this can't be fixed in the include.

But maybe you can configure your compiler to regard these includes as
system includes, because (IIRC) by default gcc will suppress warnings
from system includes.

 Ciao
     Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.