Bruce Dubbs wrote: > jp wrote: > >>> What version of the kernel is you host system running? > >> uname -r on my host returns: 2.6.29 > > Oops. I made a change to the host requirements section to require > 2.6.18 or later, but never updated the glibc instruction. The option > should be > > --enable-kernel=2.6.18 > > In both chapter 5 and 6. If you have time, I'd be interested if the > test runs OK for you when using that switch.
I don't really see a reason this flag would have any effect at all (barring bugs in the glibc kernel version compatibility code, which is one thing the test is there to find anyway... :-) ). As I said last time this came up, setting --enable-kernel newer only causes glibc to build without some compatibility code (needed for older kernels). I'm trying to envision how that would cause one of the testsuite programs to run forever, and can't come up with any valid reason. (jp: Which program was actually still running? pstree is helpful here. What was its full command line?) If I had to guess, I'd say that test sometimes loops forever and sometimes finishes (in this setup, whatever "this setup" actually is), and the --enable-kernel had no effect on this behavior other than re-running the whole testsuite. But that's just a guess... > Additionally, the behavior you describe did not occur in our test > build. Are you deviating from the book in any way? I would suspect this to be the root cause, but let's find out for sure. :-)
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
