I have a gentoo system with ~ and the build of glibc fail since an update of gcc and the linux headers, i don't know what exactly make a fail to glibc, but is here. I paste in the second post all the info build.log and emerge --info.
Created attachment 237323 [details] My full build.log in .bz2 in attachment. : /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/libc_pic.a x86_64-pc-linux-gnu-gcc -Wl,-O1 -nostdlib -nostartfiles -r -o /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/librtld.map.o '-Wl,-(' /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/dl-allobjs.os /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/libc_pic.a -lgcc '-Wl,-)' -Wl,-Map,/var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/librtld.mapT /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/libc_pic.a(init-first.os):(.data+0x0): multiple definition of `__libc_multiple_libcs' /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/dl-allobjs.os:(.bss+0xe8): first defined here /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/libc_pic.a(dl-addr.os): In function `_dl_addr_inside_object': dl-addr.c:(.text+0x0): multiple definition of `_dl_addr_inside_object' /var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/dl-allobjs.os:(.text+0x10db0): first defined here collect2: ld returned 1 exit status make[2]: *** [/var/tmp/portage/sys-libs/glibc-2.11.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/librtld.map] Erreur 1
Created attachment 237325 [details] My emerge --info in attachment.
Created attachment 237327 [details] My /etc/portage/package.use.
This is most likely a duplicate of bug #326689: glibc compile fails with -fstack-protector and -fstack-protector-all. The emerge --info shown in attachment #237325 [details] includes -fstack-protector and the error message pasted in part in comment #1 is the same as the one shown for -fstack-protector in bug #326689. I have also seen the same failure on my systems when built with -fstack-protector all, which goes away when CFLAGS are modified to exclude that switch and no other.
*** This bug has been marked as a duplicate of bug 326689 ***