[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems with --enable-gcc-warnings

From: Paul Eggert
Subject: Re: Problems with --enable-gcc-warnings
Date: Tue, 17 Dec 2013 12:49:03 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

On 12/17/2013 09:57 AM, Eli Zaretskii wrote:
> it seems like older compilers have trouble with some of the
> warning options.

Yes, --enable-gcc-warnings is currently not supported for older GCC
releases.  We've found it's enough of a pain keeping it working for
relatively-recent releases.  Currently I suspect it really needs 4.6
or later; maybe even 4.7.  Since it's a build-time option, we have
been suggesting to simply not use it if your compiler's old.

If you'd like to add support for older GCC releases, please feel free
to hack on gnulib and submit a patch; the relevant files are
m4/manywarnings.m4 and m4/warnings.m4.

> Then I had a warning in lib/file-has-acl.c, because under some
> conditions the acl_access_nontrivial doesn't return a value (look near
> its end).

I tried to fix that in trunk bzr 115573.

> Lastly, the INT_BUFSIZE_BOUND macro seems to be unable to support
> 'void *' as its argument without emitting warnings, I need to use
> intptr_t instead to pacify the compiler.

That's expected; the argument of INT_BUFSIZE_BOUND must be an integer
type or expression.  This info is in the prefatory comment.

It might be nice to have a bound for void * too, for printf %p formats.
It'd have to be a different macro though, I expect.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]