Bob Elgie <bob.el...@gmail.com> schrieb am 10:22 Dienstag, 17.Dezember 2013:
I'm unhappy with the check summary for this package. After similar results on
my first attempt, I executed
>rm -Rf gcc-4.8.1/ gcc-build
>and started the chapter again from the top. These are selected summaries from
>attempt #2 along with a small selection of FAIL notifications:
>
> === g++ Summary ===
>
># of expected passes 52310
># of unexpected failures 143
># of expected failures 290
># of unresolved testcases 143
># of unsupported tests 905
>
>FAIL: c-c++-common/asan/global-overflow-1.c -O0 (test for excess errors)
>FAIL: c-c++-common/asan/global-overflow-1.c -O3 -fomit-frame-pointer (test
>for excess errors)
><snip>
>FAIL: c-c++-common/asan/heap-overflow-1.c -Os (test for excess errors)
>FAIL: c-c++-common/asan/heap-overflow-1.c -O2 -flto -fno-use-linker-plugin
>-flto-partition=none (test for excess errors)
><snip>
>FAIL: g++.dg/asan/deep-stack-uaf-1.C -O0 (test for excess errors
><etc, etc.>
>
>
> === gcc Summary ===
>
># of expected passes 93039
># of unexpected failures 70
># of expected failures 261
># of unresolved testcases 70
># of unsupported tests 1389
>
><snip>
>FAIL: c-c++-common/asan/strncpy-overflow-1.c -O2 -flto -fno-use-linker-plugin
>-flto-partition=none (test for excess errors)
>FAIL: c-c++-common/asan/strncpy-overflow-1.c -O2 -flto -fuse-linker-plugin
>-fno-fat-lto-objects (test for excess errors)
>FAIL: c-c++-common/asan/use-after-free-1.c -O0 (test for excess errors)
><snip>
>
> === libatomic Summary ===
>
># of expected passes 17
># of unexpected failures 17
># of unsupported tests 10
>
><snip>
>FAIL: libatomic.c/atomic-exchange-3.c (test for excess errors)
>FAIL: libatomic.c/atomic-generic.c (test for excess errors)
>FAIL: libatomic.c/atomic-load-1.c (test for excess errors)
><etc, etc>
>
>There are also 24 timeouts in libmudflap.
>
>Up to this point in LFS 7.4, I haven't encountered unsolvable difficulties.
>The checks thus far in Chapter 6 have been successful.
>
>If these results are, in fact, not acceptable, how far back should I retrace
>my steps?
>
>I will be grateful for any advice.
>
>Bob Elgie
>
>Context follows:
>
>host version check:
>bash, version 4.2.45(1)-release
>/bin/sh -> /bin/dash
>Binutils: (GNU Binutils for Debian) 2.22
>bison (GNU Bison) 2.7.12-4996
>/usr/bin/yacc -> /usr/bin/bison.yacc
>bzip2, Version 1.0.6, 6-Sept-2010.
>Coreutils: 8.21
>diff (GNU diffutils) 3.2
>find (GNU findutils) 4.4.2
>GNU Awk 4.0.1
>/usr/bin/awk -> /usr/bin/gawk
>gcc (Debian 4.7.3-4) 4.7.3
>g++ (Debian 4.7.3-4) 4.7.3
>(Debian EGLIBC 2.17-92) 2.17
>grep (GNU grep) 2.14
>gzip 1.6
>Linux version 3.10-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.3
>(Debian 4.7.3-6) ) #1 SMP Debian 3.10.5-1 (2013-08-07)
>m4 (GNU M4) 1.4.16
>GNU Make 3.81
>GNU patch 2.7.1
>Perl version='5.14.2';
>sed (GNU sed) 4.2.2
>tar (GNU tar) 1.26
>Texinfo: makeinfo (GNU texinfo) 5.1
>xz (XZ Utils) 5.1.0alpha
>g++ compilation OK
>
>The host does not run 24/7. After each reboot and before entering the chroot
>environment I execute two shell scripts pasted from the early sections of
>Chapter 6:
>First (and once only)
>#!/bin/bash
># Prepare kernel filesystem
>
># Mount and populate /dev from host
>mount -v --bind /dev $LFS/dev
>
># Mount virtual kernel file systems
>mount -vt devpts devpts $LFS/dev/pts -o gid=5,mode=620
>mount -vt proc proc $LFS/proc
>mount -vt sysfs sysfs $LFS/sys
>
># test for existence of link ( -h ) to /run/shm
># mount it in the temporary system as separate from the host file system
>if [ -h $LFS/dev/shm ]; then
> link=$(readlink $LFS/dev/shm)
> if [ ! -d $LFS/$link ]; then
> mkdir -p $LFS/$link
> fi
> mount -vt tmpfs shm $LFS/$link
> unset link
>else
> mount -vt tmpfs shm $LFS/dev/shm
>fi
># END Prepare kernel filesystem
>
>Second:
>#!/bin/bash
># Change root to enter the lfs system
>chroot "$LFS" /tools/bin/env -i \
> HOME=/root \
> TERM="$TERM" \
> PS1='\u:\w\$ ' \
> PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin:/usr/local/bin \
> /tools/bin/bash --login +h
># END Change root
>
>[The PATH is extended to include /usr/local/bin because I'm using paco as a
>package manager.]
>
Hi,
at least you need to make sh a link to bash not dash. This might (or should)
solve some of your troubles. Can`t help you more...
Seba
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
