On 9/24/18 11:34 PM, lothar wrote: > hello, > > i am in lfs 8.2 book 6.2.20, gcc, where i encountered the trouble that the > test runner hung. > i killed the test runner. > in xb/gcc/testsuite/gcc/gcc.log, there were 127959 PASS, 0 FAIL, 366 XFAIL > records. > i believe the test runner was in a loop. > > i left my session and came back hours later and wanted to resume my chroot > session and retry the build. > i gave the commands shown below from lfs 8.2 book 6.2.2, 6.2.3, 6.2.4 to > resume the chroot session. > i made a fresh copy of gcc-7.3.0 sources, and did the config and make from lfs > 8.2 book 6.2.20. > when i ran the test suite, every test failed. > in xb/gcc/testsuite/gcc/gcc.log, it looks like every FAIL case has the 3 lines > > FAIL: # text with test case name > Excess errors: > spawn failed > > my question is, how can i quit my chroot session and resume it later so that > the builds work properly. > > the commands i gave to resume the chroot session are shown here: > > > > [root@localhost lfs82]# uname -a > Linux localhost.localdomain 4.16.3-301.fc28.x86_64 #1 SMP Mon Apr 23 21:59:58 > UTC 2018 x86_64 x86_64 x86_64 GNU/Linux > > # lfs 8.2 book 6.2.2: > [root@localhost lfs82]# mount -v --bind /dev $LFS/dev > > # lfs 8.2 book 6.2.3: > [root@localhost lfs82]# mount -vt devpts devpts $LFS/dev/pts -o gid=5,mode=620 > [root@localhost lfs82]# mount -vt proc proc $LFS/proc > [root@localhost lfs82]# mount -vt sysfs sysfs $LFS/sys > [root@localhost lfs82]# mount -vt tmpfs tmpfs $LFS/run >
Just a silly question, was the LFS variable set? Also, the following is missing: if [ -h $LFS/dev/shm ]; then mkdir -pv $LFS/$(readlink $LFS/dev/shm) fi > # lfs 8.2 book 6.2.4: > [root@localhost lfs82]# chroot "$LFS" /tools/bin/env -i \ > HOME=/root \ > TERM="$TERM" \ > PS1='(lfs chroot) \u:\w\$ ' \ > PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ > /tools/bin/bash --login +h > > # lfs 8.2 book 6.2.6: > (lfs chroot) root:/# exec /tools/bin/bash --login +h That one is not needed now that the /etc/passwd files has been created. > > # lfs 8.2 book 6.2.20: > > (lfs chroot) root:/# cd xh/gcc-7.3.0 You had deleted the previous build directories, haven't you? > (lfs chroot) root:/xh/gcc-7.3.0/# case $(uname -m) in > x86_64) > sed -e '/m64=/s/lib64/lib/' \ > -i.orig gcc/config/i386/t-linux64 > ;; > esac > > # rm -f /usr/lib/gcc # omitted, done previously > > (lfs chroot) root:/xh/gcc-7.3.0/# mkdir -v xb > (lfs chroot) root:/xh/gcc-7.3.0/# cd xb > > (lfs chroot) root:/xh/gcc-7.3.0/xb# SED=sed \ > (lfs chroot) root:/xh/gcc-7.3.0/xb# ../configure --prefix=/usr \ > --enable-languages=c,c++ \ > --disable-multilib \ > --disable-bootstrap \ > --with-system-zlib > (lfs chroot) root:/xh/gcc-7.3.0/xb# make > (lfs chroot) root:/xh/gcc-7.3.0/xb# make -k check > Apart from what has been said above, there is nothing obvious I can see. Pierre -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
