> The glibc error seems familiar. I think I got it when I was trying to > compile glibc 2.2.5 with gcc 2.95.2/3.
Yeah ... good suggestion. This is 3.2. I've brought the latest BINUTILS, GCC, GLIBC as well as more than a dozen supporting packages. All very current. The GLIBC error looks almost like a source code error that just never got caught before. So how come I'm tripping over it now? The situation is: I can build GLIBC, but I cannot REbuild GLIBC in a 'chroot' subshell. Some twenty other packages rebuild just find in that 'chroot' sub-world. But GLIBC and GETTEXT fail. -- RMT
