From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.bugs Subject: bug#13448: Cannot build Emacs 24.2.92 Date: Tue, 15 Jan 2013 14:08:05 -0500 Message-ID: <7phamib6y2.fsf@fencepost.gnu.org> References: <20130115175931.59dbde1f13cce8bd98fbd08b@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1358276922 16076 80.91.229.3 (15 Jan 2013 19:08:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 15 Jan 2013 19:08:42 +0000 (UTC) Cc: Xue Fuqiao , eggert@cs.ucla.edu, 13448@debbugs.gnu.org To: Andreas Schwab Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jan 15 20:08:58 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TvBsR-0003Ie-39 for geb-bug-gnu-emacs@m.gmane.org; Tue, 15 Jan 2013 20:08:51 +0100 Original-Received: from localhost ([::1]:51618 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvBsA-0004Yj-Lk for geb-bug-gnu-emacs@m.gmane.org; Tue, 15 Jan 2013 14:08:34 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:38376) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvBs8-0004Yb-Bn for bug-gnu-emacs@gnu.org; Tue, 15 Jan 2013 14:08:33 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TvBs7-00077a-BQ for bug-gnu-emacs@gnu.org; Tue, 15 Jan 2013 14:08:32 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56545) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TvBs7-00077W-8Z for bug-gnu-emacs@gnu.org; Tue, 15 Jan 2013 14:08:31 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1TvBsb-0006In-Tw for bug-gnu-emacs@gnu.org; Tue, 15 Jan 2013 14:09:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Glenn Morris Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 15 Jan 2013 19:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13448 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13448-submit@debbugs.gnu.org id=B13448.135827692124187 (code B ref 13448); Tue, 15 Jan 2013 19:09:01 +0000 Original-Received: (at 13448) by debbugs.gnu.org; 15 Jan 2013 19:08:41 +0000 Original-Received: from localhost ([127.0.0.1]:33776 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TvBsG-0006I1-0m for submit@debbugs.gnu.org; Tue, 15 Jan 2013 14:08:41 -0500 Original-Received: from fencepost.gnu.org ([208.118.235.10]:36866) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TvBsE-0006Ht-89 for 13448@debbugs.gnu.org; Tue, 15 Jan 2013 14:08:39 -0500 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1TvBrh-0001fP-Da; Tue, 15 Jan 2013 14:08:05 -0500 X-Spook: brigand fissionable JUWTF Mahmoud Ahmadinejad ASIO X-Ran: 3O!uJa9MK7h`!8*.~ZSkVdMp}u/W8A}_-|i]81U^,;,Hce:`^'Gi(D}1VC?'Ve17$9#*}f X-Hue: white X-Attribution: GM In-Reply-To: (Andreas Schwab's message of "Tue, 15 Jan 2013 19:48:46 +0100") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:69824 Archived-At: Andreas Schwab wrote: > initialized before use. But emacs shouldn't use -Wmaybe-uninitialized > anyway, since that triggers a lot of spurious warnings in various > compilers. So this is caused by use of --enable-gcc-warnings? Which is advertised as a developer option, and says "may generate false alarms when used with older or non-GNU development tools". Sounds like notabug to me. (It seems confusing if --enable-gcc-warnings actually enables _errors_ rather than warnings though.)