On Mon, Sep 08, 2014 at 03:06:49PM -0500, Bruce Dubbs wrote:
>
> Please direct any comments about this release to the LFS development team at
> lfs-...@linuxfromscratch.org. Please note that registration for the lfs-dev
> mailing list is required to avoid junk email.
>
Still building, just finished glibc. The actual output from the
tests was much more straightforward than in the past, my log ends:
scripts/merge-test-results.sh -t /building/glibc-build/
subdir-tests.sum \
. argp assert catgets conform crypt csu ctype debug dirent dlfcn
elf gmon gnulib grp gshadow hesiod iconv iconvdata inet intl io
libidn libio locale localedata login malloc manual math misc nis
nptl nptl_db nscd nss po posix pwd resolv resource rt setjmp shadow
signal socket stdio-common stdlib streams string sunrpc sysvipc
termios time timezone wcsmbs wctype \
> /building/glibc-build/tests.sum
FAIL: posix/tst-getaddrinfo4
Summary of test results:
1 FAIL
1721 PASS
121 XFAIL
3 XPASS
Makefile:321: recipe for target 'tests' failed
make[1]: *** [tests] Error 1
make[1]: Target 'check' not remade because of errors.
make[1]: Leaving directory '/building/glibc-2.20'
Makefile:9: recipe for target 'check' failed
make: *** [check] Error 2
~
And that is a lot easier to understand than how things used to be.
But for me, it means that the follwing instructions, which used to
be very helpful, now actually make things harder to understand:
make check 2>&1 | tee glibc-check-log
grep Error glibc-check-log
I save glibc-check-log separately, and it contains only the
following:
make[1]: *** [tests] Error 1
make: *** [check] Error 2
Logging the tests is probably good, but I think we should drop the
grep because it no longer useful (it doesn't say which test(s)
failed).
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
