Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Dan Kegel <dank@kegel.com>
Cc: gdb@sources.redhat.com
Subject: Re: How does one cross-compile gdbserver?
Date: Tue, 29 Jan 2002 17:50:00 -0000	[thread overview]
Message-ID: <20020129205052.B19879@nevyn.them.org> (raw)
In-Reply-To: <3C574C25.8A2F007@kegel.com>

On Tue, Jan 29, 2002 at 05:28:05PM -0800, Dan Kegel wrote:
> I'm going crazy trying to build gdb 5.1.1's gdbserver
> in a cross-development environment.
> 
> Has anyone here build one recently?
> If so, can you please post your recipe?

(Just the day for this answer...)

Same way as anything else!  You need to have a compiler capable of
building target userland binaries, and a development environment set up
for same.  You may need to run configure in the gdbserver directory
manually, with CC set appropriately.  Note that you want a gdb
configured --host=<your target>, not --target=<>!

I don't give it good odds of compiling.  I've tried several times to
clean that up and gotten stymied in various people's objections to my
methods (sorry Andrew).  I'll be taking another stab at it this week I
think.

If you get it to build, drop the list a line with your platform.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-01-30  1:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 17:22 Dan Kegel
2002-01-29 17:50 ` Daniel Jacobowitz [this message]
2002-01-29 18:22   ` Dan Kegel
2002-01-29 19:24   ` Andrew Cagney
2002-01-29 19:38     ` Dan Kegel
2002-01-29 21:20       ` Andrew Cagney
2002-01-29 21:23         ` Daniel Jacobowitz
2002-01-29 20:33     ` Daniel Jacobowitz
2002-01-29 20:44       ` Dan Kegel

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=20020129205052.B19879@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=dank@kegel.com \
    --cc=gdb@sources.redhat.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