DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:to:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=X1DWLN67qVUZbDH4
	e/j+v8lD6jmSCxvatUrxzXuTBjKgR4jGPCaXw5/BTKXNk3Bj0lGPXSSg4OMratJW
	zpIJ4fhwvgjJAMibhM9W05mX0r119AJfBpXJ40ICwBxJWNsIuw6NO4256axSxXs3
	PR2AtB6j26NNRo5rYt/lmC1dd2s=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: ldd differences
References: <56E6DA81.3050100@leidos.com> <87lh5lufh4.fsf@Rainer.invalid> <56E702EC.5060807@leidos.com> <87h9g8vptm.fsf@Rainer.invalid> <56E715EE.4030006@leidos.com>
To: <cygwin@cygwin.com>
From: Roger Wells <roger.k.wells@leidos.com>
Message-ID: <56E71DF2.1060905@leidos.com>
Date: Mon, 14 Mar 2016 16:24:18 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56E715EE.4030006@leidos.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit

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
>>> C:\cygwin64\home\roger\src\z12\z12.exe
>>>
>>> or
>>>
>>> $ 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?
>>
> 
> It was built with MinGW GCC 4.9.3 (32 bit)
> However, recall that the older 32 bit cygwin ldd had no problem with it.
> We have been using MinGW in a Cygwin environment for over two decades
> with out surprises.  I wonder if the fact that the executable is 32-bit
> is the culprit and the 64 bit Cygwin tools are expecting 64 bit items to
> work on?  I expect that ldd etc are attempting to do what the OS does
> when it loads the executable wrt identifying what resources (i.e. dll's)
> are required.  It shouldn't matter what tool built it and both 32 bit
> and 64 bit items are going to be around for a while and both need to be
> handled correctly.  I'll probably install 32 bit Cygwin and test the
> hypothesis.  I'll let you know.
> 
> 
> cheers,
> roger
> 
Here is what happens with cygcheck from a new 32 bit Cygwin install:

$ c:/cygwin/bin/cygcheck ./z12.exe
C:\cygwin64\home\roger\src\z12\z12.exe
  C:\WINDOWS\system32\KERNEL32.dll
    C:\WINDOWS\system32\ntdll.dll
    C:\WINDOWS\system32\KERNELBASE.dll
      C:\WINDOWS\system32\api-ms-win-eventing-provider-l1-1-0.dll
    C:\Program Files\TortoiseSVN\bin\api-ms-win-core-handle-l1-1-0.dll
    C:\WINDOWS\system32\api-ms-win-core-synch-l1-2-0.dll
    C:\WINDOWS\system32\api-ms-win-core-timezone-l1-1-0.dll
    C:\Program Files\TortoiseSVN\bin\api-ms-win-core-string-l1-1-0.dll
    C:\Program Files\TortoiseSVN\bin\api-ms-win-core-util-l1-1-0.dll
    C:\Program Files\TortoiseSVN\bin\api-ms-win-core-profile-l1-1-0.dll
    C:\WINDOWS\system32\api-ms-win-core-xstate-l2-1-0.dll
    C:\Program Files\TortoiseSVN\bin\api-ms-win-core-console-l1-1-0.dll
  C:\WINDOWS\system32\msvcrt.dll
  C:\cygwin64\home\roger\lib\libnmea0183.dll
    C:\MinGW\bin\libgcc_s_dw2-1.dll
    C:\MinGW\bin\libstdc++-6.dll
  C:\cygwin64\home\roger\lib\libsensors.dll
    C:\cygwin64\home\roger\lib\libutility.dll
      C:\WINDOWS\system32\ADVAPI32.DLL
        C:\WINDOWS\system32\SECHOST.dll
          C:\WINDOWS\system32\RPCRT4.dll
            C:\WINDOWS\system32\SspiCli.dll
              C:\WINDOWS\system32\CRYPTBASE.dll
                C:\WINDOWS\system32\bcryptPrimitives.dll
      C:\WINDOWS\system32\USER32.dll
        C:\WINDOWS\system32\GDI32.dll
      C:\WINDOWS\system32\WINMM.DLL
        C:\WINDOWS\system32\WINMMBASE.dll
      C:\WINDOWS\system32\WSOCK32.DLL
        C:\WINDOWS\system32\WS2_32.dll
  C:\cygwin64\home\roger\lib\libfilters.dll

Much more useful.

cheers again,
roger

>>
>> Regards,
>> Achim.
>>
> 
> 


-- 
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.wells@leidos.com

--
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