glibc does not upgrade on Gentoo Linux because of old SSP __guard symbols

Question

When I'm doing emerge -avuDN glibc always getting this:

>>> Emerging (1 of 28) sys-libs/glibc-2.15-r3
* glibc-2.15.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                       [ ok ]
* glibc-ports-2.15.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                 [ ok ]
* glibc-2.15-patches-23.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                           [ ok ]
make -s glibc-test 
make -s glibc-test 
* Scanning system for __guard to see if you need to rebuild first ... ...                                                                      [ !! ]
* Your system still has old SSP __guard symbols.  You need to
* rebuild all the packages that provide these files first:
* //bin/busybox
* //sbin/lvm.static
* //sbin/dmsetup.static
* //sbin/dmeventd.static
* //usr/bin/diet
* //usr/bin/dnsd
* //usr/bin/elftrunc
* //usr/sbin/vdu
* //usr/sbin/vps
* //usr/sbin/vtag
* //usr/sbin/nattribute
* //usr/sbin/vattribute
* //usr/sbin/chxid
* //usr/sbin/lsxid
* //usr/sbin/showattr
* //usr/sbin/vkill
* //usr/sbin/vwait
* //usr/sbin/vcontext
* //usr/sbin/setattr
* //usr/sbin/ncontext
* //usr/sbin/exec-cd
* //usr/sbin/vmemctrl
* //usr/sbin/reducecap
* //usr/sbin/vdevmap
* //usr/sbin/vdlimit
* //usr/sbin/vlimit
* //usr/sbin/vsched
* //usr/sbin/vspace 
* //usr/sbin/vuname
* //usr/sbin/vserver-info
* //usr/sbin/vserver-stat
* //usr/sbin/vrsetup
* //usr/sbin/naddress
* //usr/lib64/liblzma.so.0
* ERROR: sys-libs/glibc-2.15-r3 failed (setup phase):
*   old __guard detected
* 
* Call stack:
*              ebuild.sh, line  93:  Called pkg_setup
*   glibc-2.15-r3.ebuild, line 175:  Called eblit-run 'pkg_setup'
*   glibc-2.15-r3.ebuild, line 161:  Called eblit-glibc-pkg_setup
*        pkg_setup.eblit, line 119:  Called die
* The specific snippet of code:
*               die "old __guard detected"
* 
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.15-r3'`,
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.15-r3'`.
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.15---r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.15-r3/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.15-r3'
* S: '/var/tmp/portage/sys-libs/glibc-2.15-r3/work/glibc-2.15'

Answer 1

The error message is pretty clear. Some binaries are still using (very) old symbols. You have to rebuild the packages associated with the binaries. The error message gives you a list of these binaries.

Now you can map the binary to a package with q file /bin/busybox (you need app-portage/portage-utils for the q command).

user@host # q file /usr/bin/q
app-portage/portage-utils (/usr/bin/q)

Now emerge the package: emerge -1 app-portage/portage-utils

Answer 2

The issue, as stated in your emerge output, are the old SSP guards stemming from the listed packages. There are a few approaches to solving the issue depend. Googling around can get you a lot of cases of people working this exact issue. This case looks most similar to the problem you're having:

http://forums.gentoo.org/viewtopic-p-6903712.html?sid=128bdb308c2cb096c464a197a5980936\

I'd start here and then looks into the specifics based on your environment/settings.