From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with --enable-gcc-warnings
Date: Tue, 17 Dec 2013 23:08:02 +0200 [thread overview]
Message-ID: <83fvprchjh.fsf@gnu.org> (raw)
In-Reply-To: <52B0B8BF.9020409@cs.ucla.edu>
> 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.
next prev parent reply other threads:[~2013-12-17 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 17:57 Problems with --enable-gcc-warnings Eli Zaretskii
2013-12-17 20:49 ` Paul Eggert
2013-12-17 21:08 ` Eli Zaretskii [this message]
2013-12-17 22:20 ` Paul Eggert
2013-12-18 3:50 ` Eli Zaretskii
2013-12-18 4:13 ` Paul Eggert
2013-12-18 16:17 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fvprchjh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.