From: Ben Elliston <bje@au1.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, Dave Brolley <brolley@redhat.com>
Subject: Re: sim/sh64
Date: Mon, 19 Feb 2007 22:40:00 -0000 [thread overview]
Message-ID: <1171924726.13734.3.camel@localhost> (raw)
In-Reply-To: <20070219215131.GA8714@caradoc.them.org>
> I ran gdb_mbuild.sh today and it fell over because I didn't have
> sim/sh64. I traced this back to the modules file:
>
> date: 2002/02/28 06:07:39; author: bje; state: Exp; lines: +1 -1
> * Omit sim/testsuite/sim/sh64 for now.
>
> naked-sim -a !src/sim/sh64 !src/sim/testsuite/sim/sh64 src/sim
>
> Anyone know what that's about? Can we get rid of it now? It means
> sh64 doesn't end up in our tarballs.
In 2002 (while working at Red Hat), I contributed the sh64 port.
Through a misunderstanding with Cagney on the protocol of GDB
submission, it was sidelined with that modules change. It appears that
modules change was never reverted.
Whether sh64 is included in GDB tarballs is up to the GDB maintainers,
but yes, you could get rid of that change (modulo the usual problems of
versioning the modules file!)
Cheers, Ben
next prev parent reply other threads:[~2007-02-19 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 21:51 sim/sh64 Daniel Jacobowitz
2007-02-19 22:40 ` Ben Elliston [this message]
2007-02-20 12:43 ` sim/sh64 Daniel Jacobowitz
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=1171924726.13734.3.camel@localhost \
--to=bje@au1.ibm.com \
--cc=brolley@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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