From: Andreas Schwab <schwab@linux-m68k.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: eggert@cs.ucla.edu, 13448@debbugs.gnu.org
Subject: bug#13448: Cannot build Emacs 24.2.92
Date: Tue, 15 Jan 2013 19:48:46 +0100 [thread overview]
Message-ID: <m2wqvenuy9.fsf@igel.home> (raw)
In-Reply-To: <20130115175931.59dbde1f13cce8bd98fbd08b@gmail.com>
Xue Fuqiao <xfq.free@gmail.com> writes:
> In file included from /home/xfq/emacs-24.2.92/lib-src/make-docfile.c:250:0,
> from /home/xfq/emacs-24.2.92/lib-src/make-docfile.c:640,
> from :20:
> /home/xfq/emacs-24.2.92/lib-src/make-docfile.c: In function ‘main’:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:98:3: error: ‘type’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
> In file included from /home/xfq/emacs-24.2.92/lib-src/make-docfile.c:247:0,
> from /home/xfq/emacs-24.2.92/lib-src/make-docfile.c:640,
> from :20:
> /home/xfq/emacs-24.2.92/lib-src/make-docfile.c:627:19: note: ‘type’ was declared here
Your compiler isn't smart enough to see that the variable type is always
initialized before use. But emacs shouldn't use -Wmaybe-uninitialized
anyway, since that triggers a lot of spurious warnings in various
compilers.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-01-15 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 9:59 bug#13448: Cannot build Emacs 24.2.92 Xue Fuqiao
2013-01-15 16:15 ` Eli Zaretskii
2013-01-16 0:05 ` Xue Fuqiao
2013-01-15 17:23 ` Glenn Morris
2013-01-16 0:32 ` Xue Fuqiao
2013-01-15 18:48 ` Andreas Schwab [this message]
2013-01-15 19:08 ` Glenn Morris
2013-01-15 19:36 ` Glenn Morris
2013-01-15 20:40 ` Paul Eggert
[not found] ` <50F5BEBA.2070802@cs.ucla.edu>
2013-01-15 21:30 ` Paul Eggert
2013-01-16 1:02 ` Glenn Morris
2013-01-16 2:18 ` Paul Eggert
2013-01-16 2:26 ` Glenn Morris
2013-01-16 6:05 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wqvenuy9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=13448@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=xfq.free@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).