On Fri, 27 Jan 2006, Ken Moffat wrote:
On Fri, 27 Jan 2006, Tushar Teredesai wrote:
Maybe one of the package does this. Try this to verify that it is
indeed a problem with ldconfig.
Compile readline as follows:
./configure --prefix=/tmp/readline
make
make install
make install
ls -l /tmp/readline/lib
ldconfig -n /tmp/readline/lib
ls -l /tmp/readline/lib
--
Thanks, I'll give that a go later, certainly looks a lot quicker than doing
two full builds.
And here it is (chroot'd to one of my iterative builds). You seem to
be right, Tushar, ldconfig is indeed updating lib{history,readline}.so.5
to point to the .old versions of the correct files.
[ after second make install ]
total 2424
-rw-r--r-- 1 root root 90418 Jan 27 22:08 libhistory.a
-rw-r--r-- 1 root root 90418 Jan 27 22:07 libhistory.old
lrwxrwxrwx 1 root root 15 Jan 27 22:08 libhistory.so -> libhistory.so.5
lrwxrwxrwx 1 root root 17 Jan 27 22:08 libhistory.so.5 -> libhistory.so.5.1
-rw-r--r-- 1 root root 70246 Jan 27 22:08 libhistory.so.5.1
-rw-r--r-- 1 root root 70246 Jan 27 22:07 libhistory.so.5.1.old
-rw-r--r-- 1 root root 613284 Jan 27 22:08 libreadline.a
-rw-r--r-- 1 root root 613284 Jan 27 22:07 libreadline.old
lrwxrwxrwx 1 root root 16 Jan 27 22:08 libreadline.so -> libreadline.so.5
lrwxrwxrwx 1 root root 18 Jan 27 22:08 libreadline.so.5 ->
libreadline.so.5.1
-rw-r--r-- 1 root root 440285 Jan 27 22:08 libreadline.so.5.1
-rw-r--r-- 1 root root 440285 Jan 27 22:07 libreadline.so.5.1.old
[ after ldconfig -n ]
total 2424
-rw-r--r-- 1 root root 90418 Jan 27 22:08 libhistory.a
-rw-r--r-- 1 root root 90418 Jan 27 22:07 libhistory.old
lrwxrwxrwx 1 root root 15 Jan 27 22:08 libhistory.so -> libhistory.so.5
lrwxrwxrwx 1 root root 21 Jan 27 22:09 libhistory.so.5 ->
libhistory.so.5.1.old
-rw-r--r-- 1 root root 70246 Jan 27 22:08 libhistory.so.5.1
-rw-r--r-- 1 root root 70246 Jan 27 22:07 libhistory.so.5.1.old
-rw-r--r-- 1 root root 613284 Jan 27 22:08 libreadline.a
-rw-r--r-- 1 root root 613284 Jan 27 22:07 libreadline.old
lrwxrwxrwx 1 root root 16 Jan 27 22:08 libreadline.so -> libreadline.so.5
lrwxrwxrwx 1 root root 22 Jan 27 22:09 libreadline.so.5 ->
libreadline.so.5.1.old
-rw-r--r-- 1 root root 440285 Jan 27 22:08 libreadline.so.5.1
-rw-r--r-- 1 root root 440285 Jan 27 22:07 libreadline.so.5.1.old
I guess clfs doesn't have this problem because it is using a newer
snapshot of glibc. Does that seem reasonable ? Looking at the ldconfig
man page, anything using 'ldconfig -n /usr/lib' should not affect this,
because in the build we pass --libdir=/lib. The following packages seem
to be running an unrestricted ldconfig, according to a quick grep of the
logs : zlib, ncurses, procps - the culprit in LFS-svn must be procps.
In the alphabetical branch, I suspect that zlib will still cause this
problem (haven't looked in detail at what it does, so maybe grepping the
log has lost enough context to mislead me). Alternatively, maybe an old
version of farce has missed this.
Dan, if you are following this, does the version of farce that you are
using report a breakdown for symbolic links (number ientical, number
with different taregets) ? (if it does, the build is ok). If it
doesn't, can you take a look at /lib/libhistory.so.5 from an in-place
rebuild please, to see where it is pointing ? Thanks.
Ken
--
das eine Mal als Trag?die, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
