From: Paul Koning <pkoning@equallogic.com>
To: dje@google.com
Cc: jimb@codesourcery.com, gdb@sourceware.org
Subject: Re: gdbserver + libiberty?
Date: Tue, 15 Jan 2008 19:45:00 -0000 [thread overview]
Message-ID: <18317.3304.164946.599043@pkoning-laptop.equallogic.com> (raw)
In-Reply-To: <e394668d0801151041i10067cf9g2ead16bb70ee73eb@mail.gmail.com>
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> # We only build gdbserver automatically in a native
Doug> configuration. ...
Doug> I couldn't find any docs on building gdbserver for cross
Doug> targets (i.e --host != --target), got any pointers?
Even if the scripts don't currently do that (or not by default), it
would be good not to add additional reasons for it to be hard. I've
certainly done cross-builds of gdbserver, and they work fine.
paul
next prev parent reply other threads:[~2008-01-15 19:45 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 [this message]
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
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=18317.3304.164946.599043@pkoning-laptop.equallogic.com \
--to=pkoning@equallogic.com \
--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