On Wed, Jun 18, 2014 at 10:09:12AM +0200, Marcos Menendez wrote: > Hello, > > Sorry for the top post before. > But you are still doing it.
> One question before we continue: What did you mean with a "run once command"? > A command which you can only run one time. In this case, it uses the results of running readlink on a symlink to *overwrite* the symlink. On the next run, the result from readlink will be different. > Now to continue, I corrected the symlink and now I have this: > > root:/sources/kmod-16# ls -la /usr/lib/libz.so > lrwxrwxrwx 1 root root 23 Jun 18 10:32 /usr/lib/libz.so -> > ../../lib/libz.so.1.2.8 > > I run again the 'make check' but had the very same error. I deleted the kmod > folder and started over but nothing changed: it fails in the same part. > > Sorry for, maybe, asking the obvious, but, if the error complains about > libz.so.1 why are we working on libz.so to fix the problem? I can't figure > out the connection between both files... > I looked at what was in the book's instructions for zlib. I then assumed that one or more of the commands for moving files to /lib and then fixing the symlink had been missed or gone wrong. In my own case, I have been bitten by something similar - we used to have the version hardcoded, and I forgot to change that when a new version of zlib came out. I have assumed that the "connection" is that ldd finds a reference to libz.so in the test program, and then looks for it. Because the symlink is pointing to libz.so.1 I assume that will give this sort of error. Perhaps I am mistaken. If so, I apologise and you will have to find somebody else who understands the error better than I do. But first, what does 'file /usr/lib/libz.so' say ? And if you do have to top post, trim the old text. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
