This is the mail archive of the
mailing list for the Cygwin project.
Re: ldd differences
- From: cyg Simple <cygsimple at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 15 Mar 2016 09:32:23 -0400
- Subject: Re: ldd differences
- Authentication-results: sourceware.org; auth=none
- References: <56E6DA81 dot 3050100 at leidos dot com> <87lh5lufh4 dot fsf at Rainer dot invalid> <56E702EC dot 5060807 at leidos dot com> <87h9g8vptm dot fsf at Rainer dot invalid> <56E715EE dot 4030006 at leidos dot com> <56E71DF2 dot 1060905 at leidos dot com>
On 3/14/2016 4:24 PM, Roger Wells wrote:
> On 03/14/2016 03:50 PM, Roger Wells wrote:
>> On 03/14/2016 03:09 PM, Achim Gratz wrote:
>>> Roger Wells writes:
>>>>> Try cygcheck rather than ldd.
>>>> Thanks for responding.
>>>> Here's what happens:
>>>> $ cygcheck ./z12.exe
>>>> $ cygcheck --verbose ./z12.exe
>>>> C:\cygwin64\home\roger\src\z12\z12.exe (not x86_64 dll)
>>> Then it doesn't seem to be a Cygwin binary. Is that the product of some
>>> cross-compilation, perhaps?
> Here is what happens with cygcheck from a new 32 bit Cygwin install:
I see you figured it out. I was about to suggest that using the 64bit
ldd on a 32bit binary doesn't work. Same with cygcheck. The boundaries
of the binary data are different.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple