Ken Moffat wrote:
Hi, I'm attempting to move to a multilib system from i686. I'm already running a 64-bit x86_64 kernel, so I figured all I had to do was cross-compile the first system ("chapter 5" in conventional LFS) then chroot into that to build the full system (which would allow me to do it in an xterm with all my desktop tools available).But, I get 'no such file or directory' on /tools/bin/env and /tools/bin/bash when I try to chroot. If I use the /tools/bin/ldd shellscript, the linked libraries in /tools/lib64 are present and correct. So, is it possible to chroot to a 64-bit system while running i686 userspace with a 64-bit kernel ? The only relevant thing I could find on google was a comment on an alsa list suggesting that chrooting from 32-bit to 64-bit _is_ possible, although obviously less common. Do I need to play around with PATH, or LD_OBSCURE_MAGIC environment variables, or is this a dead end ? Ken
I've done it with my sparc. The host system is a gentoo build. I believe it has a 64-bit kernel and all the userspace is 32-bit. I started cross-compiling according to what is currently in the cross-lfs/sparc64 book and was able to chroot into the /mnt/lfs system. (Unfortunately, I had to stop there for other reasons...) So, to answer your question, it should be possible, the error must lie somewhere else.
-- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
