From: Andrew Cagney <ac131313@redhat.com>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: [commit] Mark m32r as buildable; Was: [commit] Fix missing include "dis-asm.h" in m32r-tdep.c
Date: Fri, 10 Oct 2003 01:58:00 -0000 [thread overview]
Message-ID: <3F86122B.1060302@redhat.com> (raw)
In-Reply-To: <005b01c38dff$8870da20$5169910a@KEI>
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
> Sorry. I forgot to attach the patch file.
>
>>
>> Thanks! Does the m32r now build with:
>> --enable-gdb-warnings=,-Werror
>> ?
>
>
> Yes. I built gdb with -Werror.
Thanks! I've commited the attached. It marks m32r as buildable and
that should help to stop any future bit rot - anyone making cross
architecture changes should be checking that all targets at least build
using gdb_mbuild.sh.
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 622 bytes --]
2003-10-09 Andrew Cagney <cagney@redhat.com>
* MAINTAINERS: Mark m32r-elf as buildable with -Werror.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.251
diff -u -r1.251 MAINTAINERS
--- MAINTAINERS 6 Oct 2003 20:38:17 -0000 1.251
+++ MAINTAINERS 10 Oct 2003 01:48:59 -0000
@@ -96,7 +96,7 @@
(--target=ia64-elf broken)
Kevin Buettner kevinb@redhat.com
- m32r (--target=m32r-elf broken)
+ m32r --target=m32r-elf ,-Werror
m68hc11 --target=m68hc11-elf ,-Werror ,
Stephane Carrez stcarrez@nerim.fr
prev parent reply other threads:[~2003-10-10 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 2:42 Kei Sakamoto
2003-10-08 3:06 ` Kei Sakamoto
2003-10-08 13:55 ` Andrew Cagney
2003-10-09 0:52 ` Kei Sakamoto
2003-10-10 1:58 ` Andrew Cagney [this message]
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=3F86122B.1060302@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=sakamoto.kei@renesas.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