Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: colin <colin@realtek.com.tw>, gdb@sourceware.org
Subject: Re: What are the necessary libraries to compile a cross gdb?
Date: Mon, 16 Jan 2006 13:46:00 -0000	[thread overview]
Message-ID: <20060116134607.GA31547@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0601152239o1cbdfa40uea72713bde127ddd@mail.gmail.com>

On Sun, Jan 15, 2006 at 10:39:57PM -0800, Jim Blandy wrote:
> On 1/15/06, colin <colin@realtek.com.tw> wrote:
> > Our MIPS platform contains only Linux, uClibc, and Busybox.
> > When I cross-compiling gdb, it seems to lack some libraries to successfully
> > compile it.
> > Can I use --disable-* to omit all of these libraries? What are the
> > necessaries libraries?
> 
> First, let me make sure I understand what you're trying to do.  You're
> not trying to build a GDB that runs directly on your MIPS platform;
> you're trying to build a GDB that runs somewhere else but debugs
> programs that are running on your MIPS platform.  Right?  (So you're
> not "cross-compiling" GDB; that would mean you were building a gdb
> executable which you expected to run on some other platform.  Rather,
> you're building GDB as a cross-platform debugger.)
> 
> What are the error messages you're getting?  Give us a transcript of
> the relevant part of your failing compilation, with context.

From the other direction, to cross compile GDB, you need ncurses or
some other library providing a termcap interface.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-16 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16  6:34 colin
2006-01-16  6:40 ` Jim Blandy
2006-01-16 13:46   ` Daniel Jacobowitz [this message]
2006-01-17  4:34     ` colin
2006-01-17  3:57       ` 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=20060116134607.GA31547@nevyn.them.org \
    --to=drow@false.org \
    --cc=colin@realtek.com.tw \
    --cc=gdb@sourceware.org \
    --cc=jimb@red-bean.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