Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.0.1.1.0.20040205214817.038fa600@127.0.0.1> X-Sender: Date: Thu, 05 Feb 2004 22:02:54 -0500 To: "Edward S. Peschko" , Cygwin List From: Larry Hall Subject: Re: ldd equivalent In-Reply-To: <20040206024245.GA26634@mdssdev05.comp.pge.com> References: <20040206021038 DOT GA26483 AT mdssdev05 DOT comp DOT pge DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040205213747 DOT 038e0528 AT 127 DOT 0 DOT 0 DOT 1> <20040206024245 DOT GA26634 AT mdssdev05 DOT comp DOT pge DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 09:42 PM 2/5/2004, Edward S. Peschko you wrote: >On Thu, Feb 05, 2004 at 09:38:33PM -0500, Larry Hall wrote: >> At 09:10 PM 2/5/2004, Edward S. Peschko you wrote: >> >hey, >> > >> >I was wondering if - when you ran cygcheck - it gave equivalent output to >> >ldd. >> > >> >If so, why isn't it called ldd? >> > >> >If not, what's the equivalent? >> > >> >I see mention of an 'ldd-like script' in >> > >> >http://sources.redha.com/ml/binutils/2002-09/msg00353.html >> > >> >but unfortunately, the link internal to the message seems to be broken. >> >> >> Try: >> >> http://sources.redhat.com/ml/binutils/2002-09/msg00353.html >> >> You have a typo in the URL above. >> > >well, I was there - I'm referring to the link *inside* the message. Of course. My apologies. >It points to some site which no longer exists. Quite true. >In any case, why isn't ldd bundled with binutils? Sorry, I'm not equipped to answer that. >Is it just because >ldd is implemented on top of objdump? Certainly not. Cygwin's binutils has 'objdump'. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/