From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: [RFA][3/5] New port: Cell BE SPU (the port itself)
Date: Sat, 18 Nov 2006 16:41:00 -0000 [thread overview]
Message-ID: <20061118164056.GA14861@nevyn.them.org> (raw)
In-Reply-To: <200611181109.kAIB9wWq021761@d12av02.megacenter.de.ibm.com>
On Sat, Nov 18, 2006 at 12:09:58PM +0100, Ulrich Weigand wrote:
> However, the patch has the same type of slight abuse of the build system
> that Mark was concerned about for the native patch: it has a hack to build
> a gdbserver in a "cross" configure situation. Since I can't really build
> a native spu configuration, that's the only way to actually get a gdbserver
> built I could think of ...
Well, you can build it separately. Unlike other subdirectories, the
configure script in gdb/gdbserver/ can be run directly. Is that all
you need?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-18 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 18:39 Ulrich Weigand
2006-11-11 21:19 ` Mark Kettenis
2006-11-12 15:38 ` Ulrich Weigand
2006-11-12 21:42 ` Mark Kettenis
2006-11-12 22:12 ` Daniel Jacobowitz
2006-11-13 12:27 ` Ulrich Weigand
2006-11-13 12:43 ` Mark Kettenis
2006-11-13 13:48 ` Daniel Jacobowitz
2006-11-13 19:50 ` Jim Blandy
2006-11-18 0:10 ` Ulrich Weigand
2006-11-18 6:03 ` Daniel Jacobowitz
2006-11-18 11:10 ` Ulrich Weigand
2006-11-18 16:41 ` Daniel Jacobowitz [this message]
2006-11-18 17:35 ` Mark Kettenis
2006-11-21 20:22 ` Ulrich Weigand
2006-11-21 20:40 ` Daniel Jacobowitz
2006-11-21 21:32 ` Mark Kettenis
2006-11-22 14:13 ` Ulrich Weigand
2006-11-22 18:43 ` Daniel Jacobowitz
2006-11-22 19:46 ` Ulrich Weigand
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=20061118164056.GA14861@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=uweigand@de.ibm.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