hang in gettext tests

William Harrington wwh04660 at ucmo.edu
Fri Nov 14 18:17:26 PST 2008


On Nov 14, 2008, at 6:13 PM, Ken Moffat wrote:

> On Wed, Nov 12, 2008 at 11:10:49AM +0000, Ken Moffat wrote:
>> In my build of 6.4-rc1, the box was hanging, apparently for more
>> than 10 minutes, in the gettext tests.  Last thing in the log was
>> make[3]: Entering directory
>> `/building/gettext-0.17/gettext-runtime/tests'
>> Starting test_lock ... OK
>> Starting test_rwlock ...
>>
>> I killed it with ^C, then took a look around.  Deleted test_lock
>> and test_lock.o in gettext-runtime and gettext-tools/gnulib-tests,
>> reran make check, again it hung.
>> I'm doing a fresh build, after discovering I'd only installed a few
> locales.
>
> Left the build running in gettext, used another machine, came back
> to it more than 4 hours later, it hadn't advanced.
>
> top showed
> PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 5560 root      30  10 44356  580  416 S 99.7  0.1 268:16.62 test-lock
>
> log showed
>
> make[3]: Entering directory
> `/building/gettext-0.17/gettext-runtime/tests'
> Starting test_lock ... OK
> Starting test_rwlock ...
>
> So, it _doesn't_ automatically get past any hang!
>
> Killed it.  Repeated.  The 'system activity window' on the taskbar
> in icewm shows system is busy, but firing up 'top' shows that top is
> the process using high % of cpu, which seems somewhat unlikely.
> Test log ends

I didn't test it during the build while using LFS 6.3 r2160 livecd,  
however, I didn't get this with my dual P3 1.4 system. It flew right  
past it while in the running LFS 6.4-rc1 system.

-William



More information about the lfs-dev mailing list