[Clfs-support] CLFS on Yeeloong: EGLIBC's make check fails

[Christophe Jarry]

Dear all,

I have followed CLFS HTML pages carefully to build a mips32el system on my
Lemote Yeeloong (mips64el-unknown-linux-gnu). I have chosen the "chroot" method
to build the final system. All went well until section "10.7 EGLIBC-2.13" in
which the following command:

    make -k check 2>&1 | tee eglibc-check-log; grep Error eglibc-check-log

gave me:

    make[2]: *** [/eglibc-build/math/test-double.out] Error 1
    make[2]: *** [/eglibc-build/math/test-idouble.out] Error 1
    make[1]: *** [math/tests] Error 2
    make[2]: [/eglibc-build/posix/annexc.out] Error 1 (ignored)
    make[2]: *** [/eglibc-build/rt/tst-cputimer1.out] Error 1
    make[1]: *** [rt/tests] Error 2
    make[2]: *** [/eglibc-build/debug/tst-backtrace2.out] Error 1
    make[1]: *** [debug/tests] Error 2
    make[2]: *** [/eglibc-build/elf/tst-audit1.out] Error 127
    make[2]: *** [/eglibc-build/elf/tst-audit2.out] Error 127
    make[2]: *** [/eglibc-build/elf/check-execstack.out] Error 1
    make[2]: *** [/eglibc-build/elf/check-localplt.out] Error 1
    make[1]: *** [elf/tests] Error 2
    make: *** [check] Error 2

I am particularily concerned about the "Error 127", which seems to be the most
important one (a higher number represents a more important error, right?). My
eglibc-check-log reads:

    (:snip:)
    /eglibc-build/elf/tst-audit1: no PLTREL found in
object /eglibc-build/libc.so.6
    make[2]: *** [/eglibc-build/elf/tst-audit1.out] Error 127
    (:snip:)
    /eglibc-build/elf/tst-audit2: no PLTREL found in
object /eglibc-build/libc.so.6
    make[2]: *** [/eglibc-build/elf/tst-audit2.out] Error 127
    (:snip:)

And my /eglibc-build/elf/tst-audit1.out and /eglibc-build/elf/tst-audit2.out
files read:

    version: 1
    objopen: 0,
    objopen: 0, /eglibc-build/elf/ld.so.1
    activity: add
    objsearch: libc.so.6, LA_SET_ORIG
    objsearch: /eglibc-build/libc.so.6, LA_SER_LIBPATH
    objopen: 0, /eglibc-build/libc.so.6

What do you think is the best fix to get rid of this "Error 127"?

Thank you for your suggestions,

Christophe