On my build of approximately 7.3 I got 4 failures in the procps
tests. Pierre has fixed two of them (slabtop), but now that I've
finished a minimal desktop I wanted to try to understand the other
two before I try to prove it can build itself [ _without_ analyzing
if it is bitwise the same, I've long since abandonned that ].
I can't make head or tail of what is being run. I suspect that my
absence of static libs in this build might be to blame for these
errors, but I'll note that this time the slabtop tests were ok
without the patch. The interesting part of the log is:
Running ./pgrep.test/pgrep.exp ...
ERROR: tcl error sourcing ./pgrep.test/pgrep.exp.
ERROR: can't read "tty": no such variable
while executing
"spawn $pgrep -t $tty $testproc_comm"
(file "./pgrep.test/pgrep.exp" line 83)
invoked from within
"source ./pgrep.test/pgrep.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source ./pgrep.test/pgrep.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Running ./pkill.test/pkill.exp ...
Running ./pmap.test/pmap.exp ...
FAIL: pmap extra extended output (footer)
FAIL: pmap double extra extended output (footer)
The two ERROR messages don't get counted as failures, only the two
FAIL. Any comments, or should I just quietly ignore this ?
I'll also note that the glibc tests seem to have a race in
something - on my first run, my build failed with Error 2 in the
posix tests although the only failures I could find were Error 1.
Sometimes, I really regret using set -e. Gave it what I thought
might be a fix (|| true), sailed through. Only later did I find
other tests failing (e.g. ld because of no static libs) and discover
that my attempted fix was ineffective ( set +e ... set -e works if
you want to save $? to record it in the logs or stamps ) and
therefore the second run had not hit the same failure. I guess I'm
increasingly inclined to disregard the tests - sometimes they show a
problem, but more often any test failures are inconclusive. <sigh/>
Onward to booting it again [ booted it last night before building
any of BLFS, proved that the network was ok because I could ping my
server - this is with eudev, I still had a few things to sort out
there, e.g. /dev/pts ]. Now to boot it for real and see what else
is broken ;-)
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
