From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24032 invoked by alias); 31 May 2003 00:10:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24002 invoked from network); 31 May 2003 00:10:13 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 31 May 2003 00:10:13 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19LtxS-0006wl-00; Fri, 30 May 2003 19:10:50 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19Ltwn-0005xr-00; Fri, 30 May 2003 20:10:09 -0400 Date: Sat, 31 May 2003 00:10:00 -0000 From: Daniel Jacobowitz To: Ben Giddings Cc: gdb@sources.redhat.com Subject: Re: Where do I put ncurses for ARM cross-compilation? Message-ID: <20030531001009.GA22911@nevyn.them.org> Mail-Followup-To: Ben Giddings , gdb@sources.redhat.com References: <1054336694.31812.31.camel@localhost.localdomain> <20030530232321.GA22165@nevyn.them.org> <1054338549.31812.35.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1054338549.31812.35.camel@localhost.localdomain> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-05/txt/msg00426.txt.bz2 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