glibc-2.3.5-patches-1.8.tar.bz2 and glibc-2.3.5-patches-1.9.tar.bz2 are missing from http://dev.gentoo.org/~eradicator/glibc/ which prevents sys-libs/glibc-2.3.5-r1 from emerging: # emerge glibc Calculating dependencies ...done! >>> emerge (1 of 1) sys-libs/glibc-2.3.5-r1 to / >>> Downloading http://dev.gentoo.org/~eradicator/glibc/glibc-2.3.5-patches-1.9.tar.bz2 --08:46:15-- http://dev.gentoo.org/~eradicator/glibc/glibc-2.3.5-patches-1.9.tar.bz2 => `/usr/portage/distfiles/glibc-2.3.5-patches-1.9.tar.bz2' Resolving dev.gentoo.org... 134.68.220.30 Connecting to dev.gentoo.org|134.68.220.30|:80... connected. HTTP request sent, awaiting response... 404 Not Found 08:46:15 ERROR 404: Not Found. !!! Couldn't download glibc-2.3.5-patches-1.9.tar.bz2. Aborting. As a side note, these bumps in patch level have occurred without an ebuild revision bump. That means there are potentially three different patch levels of glibc-2.3.5-r1 out there, with no obvious way to tell them apart. Assuming that the patches were changed for a reason (e.g. to fix something), this will make troubleshooting problems that much harder than if patchlevels have their own revision number. (xine-lib is another package that I've noticed slipping in new patches, but they aren't the only ones.)
The patch tarball wasn't rolled by me, but it's on the gentoo mirrors. Please try a different mirror. I've copied it to my devspace, though, so you should be able to grab it there. If changes to the patchset would effect your system, it would be bumped, but this just added support for a new architecture, so the bump is not neccessary.
