public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ben Giddings <ben@thingmagic.com>
To: gdb@sources.redhat.com
Subject: Where do I put ncurses for ARM cross-compilation?
Date: Fri, 30 May 2003 23:18:00 -0000	[thread overview]
Message-ID: <1054336694.31812.31.camel@localhost.localdomain> (raw)

Hi there,

I'm trying to cross-compile GDB to be hosted on an arm processor, but
configure complains it can't find a "term library", so I googled around
and found that people recommend I cross-compile ncurses and use that.

I managed to cross-compile ncurses, although there were errors in the
ADA bindings (which I don't plan to use, but couldn't find a way to
avoid building)

So... now what?  Where do I put the ncurses libraries so that the GDB
configure can find them?  Also, will "make" alone build both gdb and
gdbserver?  Although I want to run GDB on the host, I also might want to
run the server later.

Ben
-- 
Ben Giddings <ben@thingmagic.com>
ThingMagic LLC

             reply	other threads:[~2003-05-30 23:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 23:18 Ben Giddings [this message]
2003-05-30 23:23 ` Daniel Jacobowitz
2003-05-30 23:49   ` Ben Giddings
2003-05-31  0:10     ` Daniel Jacobowitz
2003-06-03 23:41       ` Ben Giddings

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=1054336694.31812.31.camel@localhost.localdomain \
    --to=ben@thingmagic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).