It's not particularly slow - the host is a decent laptop (i5, 2 core + hyperthreading), 16G Ram. I only gave the vm 1g and 1 cpu, but wasn't doing anything heavy apart from the lfs build at the time. The only part that might look slow is the disk - I'm using virtual box dynamic expanding disk, and if the test is expanding the amount of disk needed, then it might be getting a slow response from the storage system.
After reading a little about cilk, it is about parallel processing. I'm wondering if the fact that I gave the vm a single cpu is causing it to deadlock. I have never left the chroot environment since I created it, and I went through all the virtual filesystem mounts. In side the chroot environment mount shows: root:/sources/gcc-build# mount /dev/sdb1 on / type ext4 (rw,relatime,data=ordered) udev on /dev type devtmpfs (rw,relatime,size=497264k,nr_inodes=124316,mode=755) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) tmpfs on /run type tmpfs (rw,relatime) On Thu, Jun 11, 2015 at 5:35 PM, Bruce Dubbs <[email protected]> wrote: > Laurence Dawson wrote: > >> I'm building a pure 64 bit instance of the current dev version of LFS, and >> in chapter 6 it calls the tests for gcc critical - and I'm getting a lot >> of >> unexpected failures in the gcc test suite - I've pasted an abstract down >> below. >> >> The failures are all time outs around the cilk functionality. The >> virtualbox vm I'm building on is running a clean install of Ubuntu 15.04 >> server (no ui), with 1G ram, one cpu ( it's an Ivy Bridge Intel i3320m) >> >> Is this OK, or am I wasting my time going forward from here? >> >> --Larry >> >> root:/sources/gcc-build# ../gcc-5.1.0/contrib/test_summary | more >> cat <<'EOF' | >> LAST_UPDATED: Obtained from SVN: tags/gcc_5_1_0_release revision 222317 >> >> Native configuration is x86_64-unknown-linux-gnu >> > > === g++ Summary === >> >> # of expected passes 93224 >> # of unexpected failures 12 >> > > === gcc tests === >> > > WARNING: program timed out. >> > > === gcc Summary === >> >> # of expected passes 113913 >> # of unexpected failures 14 >> > > I have not seen that. Are you on a particularly slow system or running a > lot of other stuff at teh same time? When you entered chroot, did you > ensure all the virtual filesystems in Section 6.2 were mounted? > > -- Bruce > > > -- > http://lists.linuxfromscratch.org/listinfo/lfs-dev > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
