From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: gdbserver + libiberty?
Date: Thu, 17 Jan 2008 14:37:00 -0000 [thread overview]
Message-ID: <20080117143652.GA9907@caradoc.them.org> (raw)
In-Reply-To: <m3odbl5qhz.fsf@codesourcery.com>
On Wed, Jan 16, 2008 at 02:56:24PM -0800, Jim Blandy wrote:
>
> Daniel Jacobowitz <drow at false.org> writes:
> > On Wed, Jan 16, 2008 at 01:41:43PM -0800, Jim Blandy wrote:
> >> This is arcane magic; could we document it somewhere? gdb.texinfo's
> >> Appendix B describes "Installing GDB". gdb/README also documents
> >> configuration options, and has a section on gdbserver.
> >
> > It's in gdbserver/README currently.
>
> That says:
>
> ... building gdbserver automatically as part of building a whole
> tree of tools does not currently work if cross-compilation is
> involved (we don't get the right CC in the Makefile, to start
> with)).
>
> If this were made to work right, would that make it easier to use a
> target libiberty?
I think we could do it by moving gdbserver to the top level, but I
don't much want to do that while src still uses CVS.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-01-17 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 17:26 Doug Evans
2008-01-15 18:08 ` Jim Blandy
2008-01-15 18:42 ` Doug Evans
2008-01-15 19:45 ` Paul Koning
2008-01-15 20:24 ` Daniel Jacobowitz
2008-01-16 21:42 ` Jim Blandy
2008-01-16 22:15 ` Daniel Jacobowitz
2008-01-16 22:56 ` Jim Blandy
2008-01-17 14:37 ` Daniel Jacobowitz [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=20080117143652.GA9907@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.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