chroot error

Ronald Hummelink maillist at
Sun Mar 28 02:58:10 PST 2004

On Sun, 2004-03-28 at 10:47, Jeremy Utley wrote:

> Most commonly, this comes about because the PATH variable for the lfs
> user got changed somehow, making things stop linking against the new
> libs.
> I'd run the same sanity check on everything in /tools/bin, find out
> which packages were linked improperly, and recompile them, making sure
> that your path while your the lfs user has /tools/bin at the start.

Here is a helper:
for I in /tools/bin/*
   do echo $I
   readelf -l $I 2>&1|grep interpreter|sed -e 's%.*interpreter: \(.*\)]%\1%' |grep "^/lib"
done |grep -B1 "^/lib"

It only gives output for binaries linked to the host.


> -J-
Linux is like a small snowball rolling downhill. Microsoft is just
waiting down the mountain...


More information about the lfs-support mailing list