Hi Simon, I think that's exactly the problem. On Fri, Dec 14, 2012 at 8:45 PM, Simon Geard <delga...@ihug.co.nz> wrote:
> > "No such file or directory" doesn't always refer to the actual program > you ran (/tools/bin/bash) - it sometimes means the interpreter for the > program can't be found. If you use the same readelf command > on /tools/bin/bash, what does it tell you the interpreter is for that > program? And does it exist? > readelf -l /tools/bin/bash | grep interpreter gives: [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2] which is NOT what we want (/tools/lib64/...) Other binaries give the correct: [Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2] > > Also, what happens if you try running /tools/bin/bash from outside the > chroot, instead of inside it? Does it work there? > > It works from the outside because there IS a /lib64/ld-linux-x86-64.so.2. I'm assuming it doesn't work from the inside (i.e. chroot command gives an error) because it can't get to the interpreter requested: "/lib64/ld-linux-x86-64.so.2" Now I have to try and figure out how to fix the bash binary to look for the correct interpreter. If there's anything wrong with my reasoning please don't hesitate to correct me.
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
