Problem with ldd in cygwin 1.7.22

Problem with ldd in cygwin 1.7.22

[Peter Klotz]

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

Re: Problem with ldd in cygwin 1.7.22

[marco atzeri]

Il 7/26/2013 11:56 AM, Peter Klotz ha scritto:
> 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

try
$ cygcheck Qt5Core.dll

it will report any missing dependency.

Another matter, please also note the name scheme on cygwin is

usr/bin/cygQtCore-4.dll

I assume you are building Qt5 by yourself

Regards
Marco


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

AW: Problem with ldd in cygwin 1.7.22

[Peter Klotz]

Hello Marco

Thanks for your response.

> > 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
> 
> try
> $ cygcheck Qt5Core.dll
> 
> it will report any missing dependency.

I am aware of that but cygcheck uses an output format different from ldd. I have written a program to recursively parse library dependencies and bring them into correct order for linking.

It would be nice to use the same input for my program in Linux and Windows.


> Another matter, please also note the name scheme on cygwin is
> 
> usr/bin/cygQtCore-4.dll
> 
> I assume you are building Qt5 by yourself

The build of Qt5Core.dll was done with Visual Studio, not with cygwin/gcc.

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

Re: AW: Problem with ldd in cygwin 1.7.22

[Warren Young]

On 7/26/2013 04:38, Peter Klotz wrote:
> The build of Qt5Core.dll was done with Visual Studio, not with cygwin/gcc.

Qt is a C++ library.  C++ compiler output is not cross-compiler 
compatible.  Unless I'm wrong, and this one DLL is pure C, you're not 
going to be able to link it to a C++ program built with GCC.

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

AW: AW: Problem with ldd in cygwin 1.7.22

[Peter Klotz]

Hello Warren

> > The build of Qt5Core.dll was done with Visual Studio, not with
> cygwin/gcc.
> 
> Qt is a C++ library.  C++ compiler output is not cross-compiler
> compatible.  Unless I'm wrong, and this one DLL is pure C, you're not
> going to be able to link it to a C++ program built with GCC.

There was no intention of linking this Qt5Core.dll together with gcc compiled code. I just tried to use ldd to obtain all dependent libraries (which are compiled with Visual Studio too).

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