Am 08.11.2010 13:04, schrieb Alex Schuster: > Maximilian Bräutigam writes: > >> I'm trying to update my glibc for now 2 weeks or so and it doesn't >> matter what I'm doing, I run into a strange error. >> >> """ >> /var/tmp/portage/sys-libs/glibc-2.12.1-r3/work/build-amd64-x86_64-pc-li >> nux-gnu-nptl/libc_pic.a(init-first.os):(.data+0x0): multiple definition >> of `__libc_multiple_libcs' >> /var/tmp/portage/sys-libs/glibc-2.12.1-r3/work/build-amd64-x86_64-pc-li >> nux-gnu-nptl/elf/dl-allobjs.os:(.bss+0xe8): first defined here >> /var/tmp/portage/sys-libs/glibc-2.12.1-r3/work/build-amd64-x86_64-pc-li >> nux-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.12.1-r3/work/build-amd64-x86_64-pc-li >> nux-gnu-nptl/elf/dl-allobjs.os:(.text+0x11260): first defined here >> collect2: ld gab 1 als Ende-Status zurück >> [...] > > >> I tried many things like: playing with cflags "-fstack-protector", > > Hmm, does this mean you removed -fstack-protector? > >> downgrading gcc from 4.4.5 to 4.4.4, recompiling DEPEND packages and >> later hole @system. To my mind it is not a bug of glibc, at least I >> didn't find anything appropiate at bugs.gentoo.org and on another >> machine in office it's compiling w/o errors. > > http://bugs.gentoo.org/show_bug.cgi?id=332823 says that -fstack-protector > is supported for hardened profiles only. > > Wonko >
First, I didn't use it (cannot remember error), then I tried it out, and now I removed it again and it's compiling... Wow, thanks alot for the hint. Kind regards, der Max
