Tools contained in that stage1 package were linked dynamically with glibc 2.3.1 - after bootstrapping with glibc-2.2.5 I get errors stating, that GLIBC_2.3 can't be found. The path in the message is /lib/libc.so.6. (yes, I've tried modifying the symlinks, no joy) Reproducible: Always Steps to Reproduce: 1.Proceed as instalation says... 2.Modify /usr/portage/profiles/default-x86-1.4/packages to require <gcc-3 <glibc-2.3 3.bootstrap the system 4.See that even 'ls' is broken (but I can exit the chroot) I'll try to restore that installation by copying tools from LiveCD 1.2
1.2 tools didn't help: I get 'wc: Broken pipe' messages when bootstrapping I'll try compiling coreutils (I have them unmasked) or sh-utils. Maybe this will help...
Of course I've commented out sh-utils, fileutils, textutils and included coreutils indtead in the profile.
Instructions to downgrade to glibc-2.2.5 (WORKS!): 1.Get 1.2 LiveCD 2.Extract stage1-arch-1.2.tbz tarball from it to temporary directory 3.Edit /mnt/gentoo/usr/portage/default-architecture-1.4/packages to contain: <sys-libs/glibc-2.3 <sys-devel/gcc-3 3a.If you had gcc-3.x installed emerge sys-devel/gcc-2.95.3 and select it with gcc-config and change CFLAGS in make.conf to ones understood by gcc-2.95.3 4.Try to bootstrap the system... it will fail at ncurses rebuilding, just don't worry now 5.Reboot from (any) LiveCD 6.Copy following directories from temporary dir to / ('cp -R tempdir/dirname /'): bin sbin usr/bin usr/lib/python2.2 7.'emerge sed' 8.'emerge textutils' or 'emerge texinfo && emerge coreutils' 9.Bootstrap with option 2 ('./scripts/bootstrap.sh 2') 10.If you want, change back to gcc-3.x using 'gcc-config' or change '<sys-devel/gcc-3' in the profile to '>=sys-devel/gcc-3.2' and then 'emerge gcc'. (I DIDN'T TEST THAT!) 11.Rebuild all packages ('emerge --deep --emptytree world') or (a new installation) 'emerge system' Congratulations! You now have a Glibc-2.2.5 based system.
Changing GCC works as expected...
As per Comment #4, the issue was resolved. glibc-2.2.5 is old and outdated by gentoo standards anyways....embrace the future everyone.... Resolving as FIXED.
