>
> if I use "nm -D /usr/lib/libz.so.1.2.3" I get
> 0000a710 T inflate
> => inflate() is present in /usr/lib/libz.so.1.2.3
> (other symbols also)
>
> So I'd rather assume your setup doesn't try to link libz at all.
Correct, I ran strace with -f and it shows it tries to link to libz.a only.
15912 stat64("/usr/local/lib/libz.a", 0xff8d3a20) = -1 ENOENT (No such
file or directory)
15912 open("/usr/local/lib/libz.a", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No
such file or directory)
15912 stat64("/usr/local/lib/libz.a", 0xff8d3a20) = -1 ENOENT (No such
file or directory)
15912 open("/usr/local/lib/libz.a", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No
such file or directory)
15912 stat64("/usr/lib/perl/5.8/CORE/libz.a", 0xff8d3a20) = -1 ENOENT (No
such file or directory)
15912 open("/usr/lib/perl/5.8/CORE/libz.a", O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
15912 stat64("/usr/local/openssl/lib/libz.a", 0xff8d3a20) = -1 ENOENT (No
such file or directory)
15912 open("/usr/local/openssl/lib/libz.a", O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
15912 stat64("/usr/lib/gcc/i486-linux-gnu/4.1.2/libz.a", 0xff8d3a20) = -1
ENOENT (No such file or directory)
15912 open("/usr/lib/gcc/i486-linux-gnu/4.1.2/libz.a",
O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
15912 stat64("/usr/lib/gcc/i486-linux-gnu/4.1.2/libz.a", 0xff8d3a20) = -1
ENOENT (No such file or directory)
15912 open("/usr/lib/gcc/i486-linux-gnu/4.1.2/libz.a",
O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
15912 stat64("/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/libz.a",
{st_mode=S_IFREG|0644, st_size=89014, ...}) = 0
15912 open("/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/libz.a",
O_RDONLY|O_LARGEFILE) = 12
There is no reference to libz.so in strace output, while I do not have
libz.a on my system.
Why does linker try to link to .a only and not to .so? And how do I fix this?
>
> This surely isn't an issue about vserver, it just will not happen if you
> follow procedures carefully ;-)
Procedure I ran is the same as for host OS and it works fine with host OS.
It's some sort of problem with minimum setup of Debian as opposed to
normal installation.
Thanks for helping out with this...
--
Marcin Krol
