* checking glibc-linuxthreads-2.5.tar.bz2 ;-) ... [ ok * i386 CHOSTs are no longer supported. * Chances are you don't actually want/need i386. * Please read http://www.gentoo.org/doc/en/change-chost.xml !!! ERROR: sys-libs/glibc-2.5-r4 failed. Call stack: ebuild.sh, line 1637: Called dyn_setup ebuild.sh, line 704: Called qa_call 'pkg_setup' ebuild.sh, line 44: Called pkg_setup glibc-2.5-r4.ebuild, line 1085: Called die !!! please fix your CHOST !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.5-r4/temp/build.log'. Reproducible: Always Steps to Reproduce: 1.emerge --update --deep gnome-vfs which pulled in glibc-2.5-r4 2. 3.
(In reply to comment #0) > * i386 CHOSTs are no longer supported. > * Chances are you don't actually want/need i386. > * Please read http://www.gentoo.org/doc/en/change-chost.xml May I ask why did you file this bug?
I made a mistake not following the link. Now it works for me after manually doing the steps as described. But wouldn't it be more desirable to have some automatism (e.g. script) do all this configuration? The normal user would just like to replace the old gcc installation with a new one when upgrading to gcc 4.1.1. by using emerge and to update the old CHOST setting from i386 to e.g. i686. The script could ask questions and offer useful choices. All unnecessary manual configurations could be real showstoppers for novice users and prevent system administrators to update a system without intervention.
This won't be automated in glibc ebuild, that's what the provided documentation is for if you need to do this.
