From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, Dave Brolley <brolley@redhat.com>,
Ben Elliston <bje@au1.ibm.com>
Subject: sim/sh64
Date: Mon, 19 Feb 2007 21:51:00 -0000 [thread overview]
Message-ID: <20070219215131.GA8714@caradoc.them.org> (raw)
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.
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2007-02-19 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 21:51 Daniel Jacobowitz [this message]
2007-02-19 22:40 ` sim/sh64 Ben Elliston
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=20070219215131.GA8714@caradoc.them.org \
--to=drow@false.org \
--cc=bje@au1.ibm.com \
--cc=brolley@redhat.com \
--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