Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
	 binutils <binutils@sourceware.org>,
	Daniel Jacobowitz <drow@false.org>,
	rdsandiford@googlemail.com
Subject: Re: MIPS build failure
Date: Mon, 18 Feb 2013 19:31:00 -0000	[thread overview]
Message-ID: <5122815C.1000406@eagerm.com> (raw)
In-Reply-To: <874nh9xx61.fsf@talisman.default>

On 02/18/2013 11:02 AM, Richard Sandiford wrote:
> Michael Eager <eager@eagerm.com> writes:
>> Hi --
>>
>> I'm seeing failures building gdb-head for MIPS targets.  The
>> failure are warnings while compiling the MIPS opcode tables.  Gdb
>> is built with -Werror and the tables have missing initializers for
>> the 'exclusions' field.
>>
>> Is anyone else seeing this build failure?  If not, what are
>> you doing different from a minimal configuration?
>
> There are special makefile rules to handle this:
>
> micromips-opc.lo: micromips-opc.c
> 	$(LTCOMPILE) $(NO_WMISSING_FIELD_INITIALIZERS) -c -o $@ $<
>
> mips-opc.lo: mips-opc.c
> 	$(LTCOMPILE) $(NO_WMISSING_FIELD_INITIALIZERS) -c -o $@ $<
>
> mips16-opc.lo: mips16-opc.c
> 	$(LTCOMPILE) $(NO_WMISSING_FIELD_INITIALIZERS) -c -o $@ $<
>
> Not sure why it isn't working for gdb though.

Thanks.  That was enough of a clue.

I was picking up an old version of gcc which did not support
-Wno-missing-field-initializers.  The makefile set
$NO_WMISSING_FIELD_INITIALIZERS to null.


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


  reply	other threads:[~2013-02-18 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51226C66.3010304__32532.8041137711$1361210543$gmane$org@eagerm.com>
2013-02-18 19:03 ` Richard Sandiford
2013-02-18 19:31   ` Michael Eager [this message]
2013-02-19 14:52     ` Maciej W. Rozycki
2013-02-19 15:28       ` Michael Eager
2013-02-18 18:01 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=5122815C.1000406@eagerm.com \
    --to=eager@eagerm.com \
    --cc=binutils@sourceware.org \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=rdsandiford@googlemail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox