From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Build sh-elf with -Werror
Date: Wed, 02 Nov 2005 18:40:00 -0000 [thread overview]
Message-ID: <20051102145420.GA28462@nevyn.them.org> (raw)
In-Reply-To: <4368D237.8040704@st.com>
On Wed, Nov 02, 2005 at 02:50:31PM +0000, Andrew STUBBS wrote:
> Hi all,
>
> Following my recent mistake with the -batch-silent patch I thought I had
> better check I hadn't missed anything else due to my forgetting
> '--enable-gdb-build-warnings=,-Werror'.
>
> I found that I had not, but that the sh-elf debugger wouldn't build due
> to pre-existing problems. I guess nobody is interested in sh-elf or
> everybody forgets Werror.
The gdb_byte warnings mostly only show up with gcc4.
> The attached patch fixes the problems. Note that monitor.c actually did
> build because it is never built with Werror, but not all the warnings
> were unavoidable.
These are OK. Thanks.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-02 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 15:25 Andrew STUBBS
2005-11-02 18:40 ` Daniel Jacobowitz [this message]
2005-11-02 19:55 ` Andrew STUBBS
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=20051102145420.GA28462@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@sources.redhat.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