public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Ben Giddings <ben@thingmagic.com>
Cc: gdb@sources.redhat.com
Subject: Re: Where do I put ncurses for ARM cross-compilation?
Date: Sat, 31 May 2003 00:10:00 -0000	[thread overview]
Message-ID: <20030531001009.GA22911@nevyn.them.org> (raw)
In-Reply-To: <1054338549.31812.35.camel@localhost.localdomain>

On Fri, May 30, 2003 at 07:49:10PM -0400, Ben Giddings wrote:
> On Fri, 2003-05-30 at 19:23, Daniel Jacobowitz wrote:
> > That's a problem with your cross compiler, not with GDB.  But probably
> > it's wherever you put your C library so that GCC could find that.
> 
> Ok, any hints?  My cross-compilation environment is in /usr/local/armbe,
> I've tried putting it in the obvious places:
> 
> ben@magneto% ls /usr/local/armbe/arm-linux/lib/*curse*
> /usr/local/armbe/arm-linux/lib/libncurses.a
> /usr/local/armbe/arm-linux/lib/libncurses++.a
> /usr/local/armbe/arm-linux/lib/libncurses_g.a
> 
> ben@magneto% ls /usr/local/armbe/lib/*curse*
> /usr/local/armbe/lib/libncurses.a    
> /usr/local/armbe/lib/libncurses++.a
> /usr/local/armbe/lib/libncurses_g.a
> 
> Is there a way to find out where the cross-compilation environment is
> looking, or any other way to try to debug the process?

If that's where libc.a is, it should work.  Try sticking -v options
on the gcc command line to see what -L paths it is giving ld.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-05-31  0:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 23:18 Ben Giddings
2003-05-30 23:23 ` Daniel Jacobowitz
2003-05-30 23:49   ` Ben Giddings
2003-05-31  0:10     ` Daniel Jacobowitz [this message]
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=20030531001009.GA22911@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=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).