It would fix the issue but would hide future code that ignores warnings when they shouldn't. It seems like a toss up of damned if we do and damned if we don't so I choose annotating the code with exactly what was going on and hiding the error only for that code.
doanld On Mon, Oct 12, 2015 at 12:27 PM, Paul Jakma <[email protected]> wrote: > On Mon, 12 Oct 2015, Donald Sharp wrote: > > It sure looked like to me that it was a bit of a glibc pointing fingers at >> the gcc implementation and gcc pointing fingers at the glibc >> implementation, with a bit of not in my backyard thrown in for good >> measure. >> > > Would this 'fix' the Werror issue? ;) > > diff --git a/configure.ac b/configure.ac > index 64c591e..4e08b4c 100755 > --- a/configure.ac > +++ b/configure.ac > @@ -177,7 +177,7 @@ else > fi > > if test x"${enable_werror}" != x"no" ; then > - WERROR="-Werror" > + WERROR="-Werror -Wno-unused-result" > fi > AC_SUBST(WERROR) > > regards, > -- > Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A > Fortune: > If they were so inclined, they could impeach him because they don't like > his necktie. > -- Attorney General William Saxbe >
_______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
