From: Michael Eager <eager@eagerm.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
binutils <binutils@sourceware.org>,
Daniel Jacobowitz <drow@false.org>,
Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: MIPS build failure
Date: Tue, 19 Feb 2013 15:28:00 -0000 [thread overview]
Message-ID: <51239A05.6060408@eagerm.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1302191449520.6762@tp.orcam.me.uk>
On 02/19/2013 06:52 AM, Maciej W. Rozycki wrote:
> On Mon, 18 Feb 2013, Michael Eager wrote:
>
>>> 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.
>
> That looks like an issue to me, what version of GCC was that? Perhaps we
> should resort to -Wno-error for NO_WMISSING_FIELD_INITIALIZERS if the
> actual option is not supported.
gcc-3.4.6. (RHEL 4)
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2013-02-19 15:28 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
2013-02-19 14:52 ` Maciej W. Rozycki
2013-02-19 15:28 ` Michael Eager [this message]
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=51239A05.6060408@eagerm.com \
--to=eager@eagerm.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=macro@codesourcery.com \
--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