From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18249 invoked by alias); 6 Jun 2009 07:09:12 -0000 Received: (qmail 18238 invoked by uid 22791); 6 Jun 2009 07:09:11 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from 30.mail-out.ovh.net (HELO 30.mail-out.ovh.net) (213.186.62.213) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Sat, 06 Jun 2009 07:09:07 +0000 Received: (qmail 30238 invoked by uid 503); 6 Jun 2009 07:09:08 -0000 Received: from b7.ovh.net (HELO mail433.ha.ovh.net) (213.186.33.57) by 30.mail-out.ovh.net with SMTP; 6 Jun 2009 07:09:08 -0000 Received: from b0.ovh.net (HELO queue-out) (213.186.33.50) by b0.ovh.net with SMTP; 6 Jun 2009 07:09:02 -0000 Received: from amontpellier-156-1-152-224.w90-15.abo.wanadoo.fr (HELO ?192.168.1.20?) (piments%piments.com@90.15.79.224) by ns0.ovh.net with SMTP; 6 Jun 2009 07:09:02 -0000 Message-ID: <4A2A160E.7090400@piments.com> Date: Sat, 06 Jun 2009 07:09:00 -0000 From: peter User-Agent: Thunderbird 2.0.0.19 (X11/20090308) MIME-Version: 1.0 To: Crossgcc list Subject: how to get target ldd ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Ovh-Tracer-Id: 1588926244989119918 X-Ovh-Remote: 90.15.79.224 (amontpellier-156-1-152-224.w90-15.abo.wanadoo.fr) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00010.txt.bz2 Hi, I am having problems with a busybox ARM target I have build using ct-ng. None of the executables , including busybox, seem to work unless I build them static. Unfortunately the rather trimmed down error handling in BB is more of a distraction than a help in finding where the real problem lies. Is there a way to get ldd for the target system out of ct-ng? TIA, Peter. -- For unsubscribe information see http://sourceware.org/lists.html#faq