Hi, I did a build of the LFS trunk from 20060221 to see how things stood. Everything built as expected. The build came from my script set, so hopefully there aren't any typos since they're generated manually. I ran all of the test suites.
I had one issue with the coreutils test that was probably script
related. The tests run with `src/su dummy -c "make
RUN_EXPENSIVE_TESTS=yes check"' ran all of the tests successfully, but
my script kept hanging when the command completed. I'll have to look
at that later.
Host was anduin which is an AMD Athlon XP 2100+. Optimization flags
were off during the build. Next time I'll use some sane ones to see
if they affect the build. Attached is a file with trimmed output of
test failures. There are a handful of failures, none of which I've
analyzed.
* gcc-4.0.2
Failure in g++.dg/template/array14.C has been going on for a while
on this host. I don't
know the cause, but will try to get to the bottom of that. There
were also 6 failures in
libmudflap which are well documented. Next time I'll increase the
timeout as Greg
suggest at http://www.diy-linux.org/x86-reference-build/chroot.html#c-gcc .
* glibc-2.3.6
Failure in malloc/tst-calloc.out. Again, haven't looked into it.
Next build I'll try to
analyze this and the gcc failure.
* vim-6.4
Failure in Xtestfile. The test shows a parse error most likely
resulting from an
`undeclared identifier fd_set'.
This is just a datapoint on trunk status. If anyone has any info
about these failures, feel free to tack it on.
--
Dan
lfs-20060221-test-results
Description: Binary data
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
