Never mind, I got it, thanks. The problem was that I did not apply the "specs" patch to gcc. This fixes everything, of course, producing the right answer for
readelf -l a.out | grep ': /tools' below, and makes the chroot-ing possible. I would like to take the opportunity to suggest the CLFS gurus to include such a warning in the documentation. The importance of that patch ought to be emphasized. I skipped it, since I've compiled gcc-4.4.3, and the patch is designated for gcc-4.4.2. But then I remembered reading something long time ago in the LSF books about making the changes in the "SPECS" explicitely, which rose the suspicion that the above named patch would do that in this version of CLFS. It turned out to be true... Happy compilation to Everyone, Tibor --- On Tue, 2/2/10, Lapohos Tibor <tibor.lapo...@rogers.com> wrote: > From: Lapohos Tibor <tibor.lapo...@rogers.com> > Subject: chroot: cannot run command `/tools/bin/env': No such file or > directory > To: cross-lfs@linuxfromscratch.org > Date: Tuesday, February 2, 2010, 12:56 PM > Hello All, > > First, I built a multilib system starting with a live CD, > while workin on a USB flash memory stick. > > Next, I booted from the shiny new system on the USB stick, > and built a second multilib system on the hard disks. It is > up and running with a bunch of other things from CBLFS. > > Now, I would like to build a 64-bit only system while > booting off and working with the OS on the hard disk, and I > am geting stuck at chroot. > > My mounts are: > /dev/md1 -> / > /dev/md0 -> /boot > /dev/md2 -> /home > /dev/md3p1 -> /scratch > /dev/md3p2 -> swap > > I am building with > > CLFS = /scratch/clfs64 > > where so far I got > > /scratch/clfs64/tools > /scratch/clfs64/cross-tools > /scratch/clfs64/{dev,proc,sys} > > and > > /cross-tools -> /scratch/clfs64/cross-tools/ > /tools -> /scratch/clfs64/tools/ > > The env and chroot binaries do exist and ought to be > healthy in the /tools/bin folder. > > After exiting the > su -clfs > environment and comming back to root>, the command that > fails to change the root location is: > > chroot "${CLFS}" /tools/bin/env -i \ > HOME=/root TERM="${TERM}" > PS1='\u:\w\$ ' \ > > PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ > /tools/bin/bash --login +h > > I read whatever I could on the net, and it just doesn't > make sense to me. So far the only unorthodox point I can > think of is that ${CLFS} is not on a dedicated mount on its > own. Can this really be it? > > Furthermore, what I noticed is that, if I insert a test > like: > > ##==CH6.3===== > echo 'main(){}' > dummy.c > ${CC} dummy.c > readelf -l a.out | grep ': /tools > > I do not obtain /tools. Is this right? (I doubt it, but I > cannot tell where the problem is.) > > For the sakeness of completeness the PATH of the root is: > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/cuda/bin:/opt/firefox/bin > > I am following SVN-20100103-x86_64-Pure64, but I am using > more recent versions of the software therein. What I > compiled successfully so far is: > #= Linux-headers 2.6.32 > #= file 5.03 > #= ncurses 5.7 > #= gmp 4.3.2 > #= mpfr 2.4.2 > #= ppl 0.10.2 > #= CLooG-PPL 0.15.7 > #= binutils 2.20 > #= gcc 4.4.2 > #= eglibc 2.10.1-20090825-r8873 > #= gcc 4.4.3 > ##==CH6.3 > #= gmp 4.3.2 > #= mpfr 2.4.2 > #= ppl 0.10.2 > #= CLooG-PPL 0.15.7 > #= zlib 1.2.3 > #= binutils 2.20 > #= gcc 4.4.3 > #= bash 4.0 > #= bison 2.4.1 > #= bzip2 1.0.5 > #= coreutils 7.6 > #= diffutils 2.8.7 > #= findutils 4.4.2 > #= file 5.03 > #= flex 2.5.35 > #= gawk 3.1.7 > #= gettext 0.17 > #= grep 2.5.4 > #= gzip 1.3.12 > #= m4-1.4.13 > #= make 3.81 > #= patch 2.5.9 > #= sed 4.2.1 > #= tar 1.22 > #= texinfo 4.13a > #= vim 7.2 > #= XZ utils-4.999.9beta > ##==CH8 > #= util-linux-ng 2.16.1 > > Thanks for your help in advance, > Tibor > > -- > http://linuxfromscratch.org/mailman/listinfo/cross-lfs > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page > -- http://linuxfromscratch.org/mailman/listinfo/cross-lfs FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page