From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2769 invoked by alias); 30 May 2003 23:49:14 -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 2689 invoked from network); 30 May 2003 23:49:13 -0000 Received: from unknown (HELO smtp01.exodus.net) (216.34.163.231) by sources.redhat.com with SMTP; 30 May 2003 23:49:13 -0000 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp01.exodus.net (8.12.9/8.12.9) with ESMTP id h4V0Z2Xi028642 for ; Fri, 30 May 2003 19:35:03 -0500 Received: from [10.0.0.42] (unverified [66.228.91.169]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id ; Fri, 30 May 2003 16:49:12 -0700 Subject: Re: Where do I put ncurses for ARM cross-compilation? From: Ben Giddings To: Daniel Jacobowitz Cc: gdb@sources.redhat.com In-Reply-To: <20030530232321.GA22165@nevyn.them.org> References: <1054336694.31812.31.camel@localhost.localdomain> <20030530232321.GA22165@nevyn.them.org> Content-Type: text/plain Organization: ThingMagic LLC Message-Id: <1054338549.31812.35.camel@localhost.localdomain> Mime-Version: 1.0 Date: Fri, 30 May 2003 23:49:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00425.txt.bz2 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? Ben