I feel silly replying to myself again -- but...after re-running the 
check, and it coming up OK...  I went ahead and went to install this 
glibc... the tail end of the error message (I assume this is relating to 
a manual//info?) is as follows.  Not sure if this is OK/normal/whatever.

make[2]: Entering directory `/sources/glibc-2.14.1/manual'
pwd=`pwd`; \
no libm-err-tab.pl $pwd/.. > libm-err-tmp
/bin/sh: line 1: no: command not found
make[2]: *** [stamp-libm-err] Error 127
make[2]: Leaving directory `/sources/glibc-2.14.1/manual'
make[1]: *** [manual/subdir_install] Error 2
make[1]: Leaving directory `/sources/glibc-2.14.1'
make: *** [install] Error 2
I have no name!:/sources/glibc-build#

---
====================================
David Scott Williams

twitter: @dscott_williams
blog: http://deadpenguinsociety.org
====================================

On 29.11.2011 09:58, David Scott Williams wrote:
> Now -- this is funny, I re-ran:
> ===
> I have no name!:/sources/glibc-build# make -k check 2>&1 | tee
> glibc-check-log
> ====
> And it seems to have done OK on the second run...
>
> ====
> I have no name!:/sources/glibc-build# grep Error glibc-check-log
> I have no name!:/sources/glibc-build#
> =====
>
> Weird.
>
>
>
> ---
> ====================================
> David Scott Williams
>
> twitter: @dscott_williams
> blog: http://deadpenguinsociety.org
> ====================================
>
> On 29.11.2011 09:49, David Scott Williams wrote:
>> Actually, this is my entire list:
>> make[2]: *** [/sources/glibc-build/libio/tst-fopenloc.check] Error
>> 127
>> make[1]: *** [libio/tests] Error 2
>> make[2]: *** [/sources/glibc-build/posix/bug-regex32.out] Error 1
>> make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored)
>> make[2]: *** [/sources/glibc-build/posix/bug-regex2-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/bug-regex14-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/bug-regex21-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/bug-regex31-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/tst-rxspencer-mem] Error 
>> 127
>> make[2]: *** [/sources/glibc-build/posix/tst-pcre-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/tst-boost-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/bug-glob2-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/tst-vfork3-mem] Error 127
>> make[2]: *** [/sources/glibc-build/posix/tst-fnmatch-mem] Error 127
>> make[1]: *** [posix/tests] Error 2
>> make[2]: *** [/sources/glibc-build/misc/tst-error1-mem] Error 127
>> make[1]: *** [misc/tests] Error 2
>> make[2]: *** [/sources/glibc-build/nptl/tst-stack3-mem] Error 127
>> make[1]: *** [nptl/tests] Error 2
>> make[2]: *** [/sources/glibc-build/elf/tst-leaks1-mem] Error 127
>> make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127
>> make[1]: *** [elf/tests] Error 2
>> make: *** [check] Error 2
>>
>> I assume I have failed?
>>
>> ---
>> ====================================
>> David Scott Williams
>>
>> twitter: @dscott_williams
>> blog: http://deadpenguinsociety.org
>> ====================================
>>
>> On 29.11.2011 09:28, David Scott Williams wrote:
>>> When building and installing (6.9) the glibc ... what test errors
>>> are
>>> acceptable?  What are the guidelines for determining "quirkiness"
>>> vs.
>>> "woops, I screwed up" ?
>>>
>>> For example, the following error (and a refusal to finish the make)
>>> ..
>>> I assume to be bad:
>>> make[2]: *** [/sources/glibc-build/elf/noload-mem] Error 127 
>>> Scratch
>>>
>>> I am in the process of doing it again (re-patch/etc..) and see what
>>> happens.  I am building on a 2.6.32 kernel, and I might very well
>>> have
>>> left the 2.6.25 in the copied shell command...
>>>
>>> However, I was just wondering what tests, when they fail, are FAIL
>>> rather than fail;)  :) ?
>>>
>>> --
>>> ====================================
>>> David Scott Williams
>>>
>>> twitter: @dscott_williams
>>> blog: http://deadpenguinsociety.org
>>> ====================================

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to