chroot error

Floyd Hagen flohagen at montanadsl.net
Sun Mar 28 18:12:43 PST 2004


Thanks guys.  Looks like I got quite a few that are linked wrong.  I
think this will have to wait till next weekend.

On Sun, Mar 28, 2004, Ronald Hummelink wrote:
> 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.
> 
> Ronald
> 
> > -J-
> -- 
> Linux is like a small snowball rolling downhill. Microsoft is just
> waiting down the mountain...
> 
> 
> 
> !DSPAM:4066b0d7294551191326629!
> 
> 
> -- 
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page



More information about the lfs-support mailing list