problem with executables

Dennis J Perkins dperkins at
Sat Nov 26 13:12:47 PST 2005

> I suspect the OP's problem is more fundamental than that. That "No such file
> or directory" error message is often caused by a bad dynamic linker path
> embedded in the binary (PT_INTERP) which can be checked using readelf eg:

I had this message a couple of days ago when I tried to chroot when
building Cross LFS.  I had to build enough packages to make a minimal
bootble system because my host system couldn't run 64-bit executables.

More information about the cross-lfs mailing list