Date: Wed, 7 Mar 2012 12:57:03 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ldd fails when dll has no execute permissions
Message-ID: <20120307175703.GA30404@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1331141199 DOT 1263 DOT YahooMailNeo AT web36701 DOT mail DOT mud DOT yahoo DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1331141199.1263.YahooMailNeo@web36701.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed, Mar 07, 2012 at 09:26:39AM -0800, cppjavaperl wrote:
>Then I tried it on an old machine running SuSE 9.0 (kernel 2.4.21, even).
>In this case, ldd fails only if the *program's* executable has no execute 
>permissions.? The dependent DLLs are not required to have executable 
>permissions -- all the dependent DLLs were enumerated whether they had the
>executable permissions or not.

I'll try to be clearer.  We obviously know how to scan an executable for
dependent DLLs since cygcheck does it already (and actually cygwin
itself does this) but we are not going to be modifying ldd to deal with
the case of non-executable binaries.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple