From: Peter Klotz <Peter.Klotz@ith-icoserve.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Problem with ldd in cygwin 1.7.22
Date: Fri, 26 Jul 2013 10:41:00 -0000 [thread overview]
Message-ID: <FDCF7296051FAA4B967818014FE88B23F3512EB656@hermes.ith-icoserve.com> (raw)
The output of ldd (32Bit) in cygwin 1.7.22 is not as expected if a single dependency cannot be found.
Correct output (all dependencies present):
$ ldd Qt5Core.dll
ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x778b0000)
kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x76eb0000)
KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll (0x76be0000)
USER32.dll => /cygdrive/c/Windows/syswow64/USER32.dll (0x75110000)
GDI32.dll => /cygdrive/c/Windows/syswow64/GDI32.dll (0x75330000)
LPK.dll => /cygdrive/c/Windows/syswow64/LPK.dll (0x75100000)
USP10.dll => /cygdrive/c/Windows/syswow64/USP10.dll (0x753c0000)
msvcrt.dll => /cygdrive/c/Windows/syswow64/msvcrt.dll (0x76ca0000)
ADVAPI32.dll => /cygdrive/c/Windows/syswow64/ADVAPI32.dll (0x76900000)
sechost.dll => /cygdrive/c/Windows/SysWOW64/sechost.dll (0x75490000)
RPCRT4.dll => /cygdrive/c/Windows/syswow64/RPCRT4.dll (0x76520000)
SspiCli.dll => /cygdrive/c/Windows/syswow64/SspiCli.dll (0x74f90000)
CRYPTBASE.dll => /cygdrive/c/Windows/syswow64/CRYPTBASE.dll (0x74f80000)
ole32.dll => /cygdrive/c/Windows/syswow64/ole32.dll (0x76d50000)
WS2_32.dll => /cygdrive/c/Windows/syswow64/WS2_32.dll (0x76100000)
NSI.dll => /cygdrive/c/Windows/syswow64/NSI.dll (0x76c90000)
icuin51.dll => /home/user/Qt-5.1.0/x86/icuin51.dll (0x49e80000)
icuuc51.dll => /home/user/Qt-5.1.0/x86/icuuc51.dll (0x4a0f0000)
icudt51.dll => /home/user/Qt-5.1.0/x86/icudt51.dll (0x7b0000)
MSVCR100.dll => /cygdrive/c/Windows/system32/MSVCR100.dll (0x74200000)
MSVCP100.dll => /cygdrive/c/Windows/system32/MSVCP100.dll (0x742c0000)
IMM32.DLL => /cygdrive/c/Windows/system32/IMM32.DLL (0x750a0000)
MSCTF.dll => /cygdrive/c/Windows/syswow64/MSCTF.dll (0x76830000)
Questionable output (a single dependency, icuin51.dll, is missing):
$ ldd Qt5Core.dll
ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x778b0000)
kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x76eb0000)
KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll (0x76be0000)
??? => ??? (0x66d10000)
??? => ??? (0x75110000)
??? => ??? (0x75330000)
??? => ??? (0x75100000)
??? => ??? (0x753c0000)
??? => ??? (0x76ca0000)
??? => ??? (0x76900000)
??? => ??? (0x75490000)
??? => ??? (0x76520000)
??? => ??? (0x74f90000)
??? => ??? (0x74f80000)
??? => ??? (0x76d50000)
??? => ??? (0x76100000)
??? => ??? (0x76c90000)
My intention was to find out the dependencies of Qt5Core.dll in order to satisfy them. This seems not possible in Windows.
The Linux version of ldd in this case prints a line like the following:
icuin51.so => not found
It would be great if the Windows version of ldd could behave the same (or at least similar).
Regards, Peter.
--
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
next reply other threads:[~2013-07-26 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 10:41 Peter Klotz [this message]
2013-07-26 11:26 ` marco atzeri
2013-07-26 12:08 ` AW: " Peter Klotz
2013-07-27 0:32 ` Warren Young
2013-07-27 5:45 ` AW: " Peter Klotz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FDCF7296051FAA4B967818014FE88B23F3512EB656@hermes.ith-icoserve.com \
--to=peter.klotz@ith-icoserve.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).