Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: gdb-7.6 branch build failures
Date: Mon, 28 Oct 2013 16:15:00 -0000	[thread overview]
Message-ID: <526E8D82.4080700@eagerm.com> (raw)

Hi --

I'm seeing build failures on the gdb_7_6-branch:

src/gdb_7_6-branch/gdb/opcodes/mips-opc.c:214: warning: missing initializer
/src/gdb_7_6-branch/gdb/opcodes/mips-opc.c:214: warning: (near initialization for 
`mips_builtin_opcodes[0].exclusions')

The failures are in opcodes/mips16-opc.c and opcodes/mips-opc.c,
and are caused by -Werror treating warnings about missing trailing
initializers as errors.  On gdb-head, these files have been
updated to explicitly initialize trailing fields with zeros.

Is anyone building gdb_7_6-branch without these errors?
If not, I'll submit a patch for the branch to turn off
-Werror for these files.

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


             reply	other threads:[~2013-10-28 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 16:15 Michael Eager [this message]
2013-10-28 18:29 ` Tom Tromey
2013-10-28 18:42   ` Michael Eager

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=526E8D82.4080700@eagerm.com \
    --to=eager@eagerm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox