On Thu 2018-06-07 (01:04), Andrey Repin wrote:
> Then I'm at a loss to explain the behavior. If he ran ldd on the same system
> he had built it (and where it is running properly), then there's environmental
> conditions involved.
Windows 7 32 bit build system:
/sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a
CYGWIN_NT-6.1-WOW windoof 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin
/sw/cygwin-7_32/jed-0.99-20_116/bin: ldd jed
ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x76fb0000)
kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x74af0000)
KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll
(0x75860000)
cygslang-2.dll => /sw/cygwin-7_32/jed-0.99-20_116/bin/cygslang-2.dll
(0x65400000)
cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
cyggcc_s-1.dll => /usr/bin/cyggcc_s-1.dll (0x6f900000)
Transfered to Windows 8 32 bit:
/sw/cygwin-7_32/jed-0.99-20_116/bin: uname -a
CYGWIN_NT-6.3 W8-64 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
/sw/cygwin-7_32/jed-0.99-20_116/bin: ldd jed
ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ff880fa0000)
??? => ??? (0x77320000)
wow64.dll => /cygdrive/c/Windows/SYSTEM32/wow64.dll (0x772d0000)
wow64win.dll => /cygdrive/c/Windows/system32/wow64win.dll (0x77260000)
wow64cpu.dll => /cygdrive/c/Windows/system32/wow64cpu.dll (0x77250000)
/sw/cygwin-7_32/jed-0.99-20_116/bin: ll /usr/bin/cygwin1.dll
-rwxr-xr-x admin None 3,195,569 2018-02-02 15:18:49 /usr/bin/cygwin1.dll
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<944481618.20180607010...@yandex.ru>
--
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
