hi
This is the first time i'm trying an lfs build. And i've followed the book
absolutely (SVN-20061226-x86_64-Multilib)
In chapter 10 glibc build i came across the following errors
malloc: using debugging hooks
make[2]: [/sources/glibc-build/posix/annexc.out] Error 1
(ignored)
make[2]: *** [/sources/glibc-build/nptl/tst-cancel1.out] Error 1
make[1]: *** [nptl/tests] Error 2
make: *** [check] Error 2
the book suggests that the first error can be ignored.
I searched on google and through the mailing lists but could not find a
solution for the tst-cancel1.
The tst-cancel1.out file is empty.
Any help would be appreciated.
Arjun
Well, I had the same errors for the 32-bit build for x86_64-Multilib
and as far as I can tell, they haven't caused any problems. Like you,
I was unable to find anything helpful online and no one ever responded
to my post to CLFS-Support with a solution. However, as I said, I
don't think that it's actually a big problem. In the 64-bit build I
got additional errors:
make[2]: *** [/usr/src/glibc/glibc-build/libio/tst-wmemstream1.out] Error 1
make[2]: *** [/usr/src/glibc/glibc-build/libio/tst-wmemstream2.out] Error 1
make[2]: *** [/usr/src/glibc/glibc-build/libio/bug-wmemstream1.out] Error 1
make[1]: *** [libio/tests] Error 2
make[2]: [/usr/src/glibc/glibc-build/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancel1.out] Error 1
make[1]: *** [nptl/tests] Error 2
make: *** [check] Error 2
I assume that the wmemstream errors are related to unicode which isn't
going to work on a CLFS system anyway. The other two errors are the
same as the 32-bit build. In any case, I haven't had any problems
from those errors. So, if you have the same errors as I do, I
wouldn't worry about it too much. It'd be great if there was a way to
get rid of them, but I haven't a clue how and as far as I can tell, my
glibc works just fine. I'm currently working on CBLFS, so I've
managed to go quite a ways on a glibc with the errors listed above.
If you haven't found anything interesting online that tells you what
the problem is and how to fix it, I'd suggest that you just continue
with CLFS and don't worry about it.
- Jonathan M Davis
_______________________________________________
Clfs-support mailing list
Clfs-support@lists.cross-lfs.org
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
