jp wrote: > Re-using the tools dir that I had got backed up, I re-runned glibc chapter 6 > with --enable-kernel=2.6.18 and tests results are even worse than with -- > enable-kernel=2.6.0: > > <...> > > I can see a process still running after the tests, see below ( I used ps axww > from my host to get it ). > > Now it's a bit late for me. Tomorrow, will restart the build from the > beginning, to make sure.
I'm also not sure whether this will have any effect -- but sure, it's worth
a try. :-)
> the command still running after the tests was: /sources/glibc-
> build/elf/ld-linux.so.2 --library-path /sources/glibc-build:/sources/glibc-
> build/math:/sources/glibc-build/elf:/sources/glibc-build/dlfcn:/sources/glibc-
> build/nss:/sources/glibc-build/nis:/sources/glibc-build/rt:/sources/glibc-
> build/resolv:/sources/glibc-build/crypt:/sources/glibc-build/nptl
> /sources/glibc-build/nptl/tst-mutex9
tst-mutex9.c tests a whole bunch of things related to pthread_mutex_*
calls...
What's in the corresponding *.out file? What do you get if you strace this
same command line? What do you get if you strace this same command line,
and make strace follow the children of forks? ("strace -otrace -ff
/sources/glibc-build/elf/ld-linux.so.2 ..." will write each PID's strace
output to the file "trace.$PID".)
>> I would suspect this to be the root cause, but let's find out for sure.
>
> Brian, I don't think I deviated from the book. I start the whole build again,
> and will double check that I don't deviate.
OK. What hardware is this?
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
