Summary: | sys-libs/glibc-2.6: configure: error: linker with -z nodelete support required - gcc 3.x issue? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Skwar <askwar> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED WONTFIX | ||
Severity: | normal | CC: | jackdachef, thomasheinz, toolchain |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log of glibc-2.6 |
Description
Alexander Skwar
2007-07-24 07:55:20 UTC
Created attachment 125845 [details]
build.log of glibc-2.6
In config.log, I find: configure:5548: checking for -z nodelete option configure:5560: i686-pc-linux-gnu-gcc -march=athlon-xp -pipe -O2 -fno-strict-aliasing -fno-stack-protector -nopie -Wl,-O1 -fPIC -shared -o conftest.so conftest.c -nostartfiles -nostdlib -Wl,--enable-new-dtags,-z,nodelete 1>&5 i686-pc-linux-gnu-gcc: -shared and -static|pie|fPIE|fpie|fno-PIC|fno-pic|nopie are incompatible configure:5563: $? = 1 configure:5568: error: linker with -z nodelete support required you most likely have binutils-2.16.1 set as your default. dont do that. (In reply to comment #3) > you most likely have binutils-2.16.1 set as your default. dont do that. Hm. You were right. I still had 2.16.1 set as default. However, even after changing to 2.17, I get this error. askwar@hetzner ~ $ eselect binutils list Installed binutils for target i686-pc-linux-gnu [1] 2.16.1 [2] 2.17 * Do I need to do something after changing binutils with eselect (I logged out and back in to the system after I ran eselect)? drop the USE=hardened as well (In reply to comment #5) > drop the USE=hardened as well > It is already disabled: [ebuild R ] sys-libs/glibc-2.6 USE="-build -debug -glibc-compat20 glibc-omitfp (-hardened*) (-multilib) nls -profile (-selinux)" 0 kB [0] you'll need to drop it from make.conf and rebuild your gcc ... most likely it has munged up your toolchain (In reply to comment #7) > you'll need to drop it from make.conf and rebuild your gcc ... most likely it > has munged up your toolchain That did it. I upgraded GCC to 4.2 and I'm now able to compile glibc. Thanks for your help! *** Bug 195961 has been marked as a duplicate of this bug. *** Switching to i686-pc-linux-gnu-3.4.6-hardenednopie profile (see gcc-config -l) solves the problem. However, it would be nice to be able to build glibc using hardened gcc. Is there a workaround for this or is it currently impossible to build a hardened glibc-2.6? |