On Thu, Dec 29, 2011 at 06:34:07PM +0000, Ken Moffat wrote:
> On Sat, Dec 24, 2011 at 12:49:55PM +0000, Andrew Benton wrote:
> >
> > For what it's worth, I've managed to reduce the number of static libs
> > to 8, all from gcc, binutils or glibc:
> >
> > andy@eccles:~$ ls /usr/lib/*.a
> > /usr/lib/libc_nonshared.a /usr/lib/libmcheck.a
> > /usr/lib/libg.a /usr/lib/libpthread_nonshared.a
> > /usr/lib/libiberty.a /usr/lib/librpcsvc.a
> > /usr/lib/libieee.a /usr/lib/libsupc++.a
> >
> > It may be possible to get rid of some of these, but fiddling with them
> > got time consuming so I gave up.
> >
> Yeah, very time-consuming (move to a new name, build an LFS system,
> see what breaks.
>
This time (still LFS-7.0), module-init-tools (needs libc.a or
else --disable-static-tools) and sysvinit (specifically, sulogin -
it couldn't find libcrypt although the symlink from libcrypt.so to
/lib/libcrypt.so.1 to libcrypt-2.14 looks ok, running ldd on it
from the host reported
/mnt/lfs/usr/lib/libcrypt.so: /lib/libc.so.6: version `GLIBC_2.14'
not found (required by /mnt/lfs/usr/lib/libcrypt.so)
linux-vdso.so.1 => (0x00007fffaa3ff000)
libc.so.6 => /lib/libc.so.6 (0x00007f7ac3927000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7ac3ca8000)
- possibly the error message is from running on the older host,
but I couldn't persuade sulogin to build until I made the static
libcrypt.a visible.
It's now building its new kernel, so LFS has completed without
other issues caused by hiding more toolchain libs. I wonder what will
break in the rest of the build.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
