From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>, Paul Koning <paul_koning@Dell.com>
Subject: Re: [RFC] configure.tgt: Update mips*-*-* to use remote-mips.o
Date: Thu, 20 Jan 2011 00:55:00 -0000 [thread overview]
Message-ID: <20110119164407.2deca0ad@mesquite.lan> (raw)
In-Reply-To: <4D375DB2.1030906@vmware.com>
On Wed, 19 Jan 2011 13:54:58 -0800
Michael Snyder <msnyder@vmware.com> wrote:
> I think mips-*-elf is appropriate.
Below is a revised patch which adds a mips*-*-elf stanza.
Kevin
* configure.tgt (mips*-*-elf): New; just like mips*-*-*, but
with remote-mips.o added to gdb_target_obs.
Index: configure.tgt
===================================================================
RCS file: /cvs/src/src/gdb/configure.tgt,v
retrieving revision 1.241
diff -u -p -r1.241 configure.tgt
--- configure.tgt 14 Jan 2011 18:16:34 -0000 1.241
+++ configure.tgt 19 Jan 2011 23:34:33 -0000
@@ -371,6 +371,11 @@ mips64*-*-openbsd*)
gdb_target_obs="mips-tdep.o mips64obsd-tdep.o \
corelow.o solib.o solib-svr4.o"
;;
+mips*-*-elf)
+ # Target: MIPS ELF
+ gdb_target_obs="mips-tdep.o remote-mips.o"
+ gdb_sim=../sim/mips/libsim.a
+ ;;
mips*-*-*)
# Target: MIPS
gdb_target_obs="mips-tdep.o"
next prev parent reply other threads:[~2011-01-20 0:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 21:20 Kevin Buettner
2011-01-19 21:39 ` Paul Koning
2011-01-19 21:50 ` Michael Snyder
2011-01-19 21:55 ` Kevin Buettner
2011-01-19 21:55 ` Michael Snyder
2011-01-20 0:55 ` Kevin Buettner [this message]
2011-01-20 5:58 ` Michael Snyder
2011-01-20 16:19 ` Ulrich Weigand
2011-01-21 1:14 ` Kevin Buettner
2011-01-21 12:44 ` Ulrich Weigand
2011-01-24 21:52 ` Kevin Buettner
2011-01-24 21:58 ` Joel Brobecker
2011-01-24 23:01 ` Kevin Buettner
2011-01-19 22:02 ` Paul Koning
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=20110119164407.2deca0ad@mesquite.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=paul_koning@Dell.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).