Gentoo Linux glibc-2.16 died :(

gistfile1.txt

 * Messages for package sys-libs/glibc-2.15-r3:

 * The ebuild phase 'postrm' has been killed by signal 11.
 * The 'postrm' phase of the 'sys-libs/glibc-2.15-r3' package has failed
 * with exit value 1.
 * 
 * The problem occurred while executing the ebuild file named
 * 'glibc-2.15-r3.ebuild' located in the '/var/db/pkg/sys-
 * libs/glibc-2.15-r3' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 * 
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.

 * Messages for package sys-libs/glibc-2.16.0:

 * Defaulting /etc/host.conf:multi to on
 * The ebuild phase 'postinst' has been killed by signal 11.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.