Re: Problems with --enable-gcc-warnings

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 17 Dec 2013 12:49:03 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: emacs-devel@gnu.org
> 
> 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.

How about some warning for older GCCs, or maybe even refusing to turn
on the compiler warnings in that case?

> > 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.

Thanks.

> > 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.

OK, thanks.