On Sun, Dec 31, 2006 at 06:27:39AM -0800, Jonathan Davis wrote: > > 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.
Sorry, your post must have slipped under my radar, maybe because I hadn't used 2.5 at the time. I could have saved writing my previous reply if I'd been a minute or two later ;-) > 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. Thanks for sharing these, so that we know what to expect. I've got some unicode working on my recent clfs-1.0.0 systems (in X, I think we need something else to get it working at all on the console), and I think I've even got UTF-8 manpages working (amazing how many people put 'smart-quotes' into manpages in english, e.g. for smartmontools). Very possibly, the temporary system might need something, but I think all the widec support comes later (e.g. the final ncurses, vim) so it could equally be something else entirely, such as bash in the temporary system. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
