Marcos Menendez wrote:
In an another attempt to solve the problem, I reinstalled zlib and
the kmod again, but the problem persists.
I tried to go deeper into the issue going into the testsuite dir and
trying to understand how it works having a look at test-modprobe.c.
I couldn't find there anything that could point me to something.
Since this is a testsuite error I don't know how critical this would
be so I will ignore it and go ahead to see what happens.
It helps to trim posts as well as bottom post.
I've read through the thread. What you should have is:
# find / -name libz.so\* -ls
lrwxrwxrwx root 23 /usr/lib/libz.so -> ../../lib/libz.so.1.2.8
-rwxr-xr-x root 113344 /lib/libz.so.1.2.8
lrwxrwxrwx root 13 /lib/libz.so.1 -> libz.so.1.2.8
(slightly edited to fit)
If you don't have that, make it so:
# ln -sfvn ../../lib/libz.so.1.2.8 /usr/lib/libz.so
# ln -sfvn libz.so.1.2.8 /lib/libz.so.1
Then tell the system to be sure:
# ldconfig
Also check the library:
# file /lib/libz.so.1.2.8
/lib/libz.so.1.2.8: ELF 64-bit LSB shared object, x86-64, version 1
(SYSV), dynamically linked, not stripped
If you still get the error that it can't find libz.so.1, then you have a
fairly serious problem. It's not a kmod issue, but a more general
problem.
You can check with a test program:
$ cat > ztest.c << EOF
#include <zlib.h>
#include <stdio.h>
int main()
{
const char* v = zlibVersion();
printf( "zlib version is %s\n", v );
}
EOF
$ gcc -o ztest -lz ztest.c
$ ./ztest
zlib version is 1.2.8
Note that /lib/libz.so.1 is used at run time, but /usr/lib/libz.so is
used when a file is linked against -lz.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
