| Summary: | modutils-2.4.25 doesn't compile with -fstack-protector | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | meyerm |
| Component: | New packages | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | gcc-porting |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
meyerm
2003-11-28 06:21:59 UTC
*** Bug 34620 has been marked as a duplicate of this bug. *** Can you please tell us what problems you are getting when you do use "-fstack-protector"? Sure, sorry for forgetting it. The last few line of the emerge are shown below. I already read in the forums that someone else had problem with modutils in combination with -fstack-protector. BTW: sash can't be compiled if glibc has been compiled with -fstack-protector (already filed a bug report 34622, but perhaps this could help you to track down the problem?). # emerge modutils [...] gcc -O2 -fomit-frame-pointer -funroll-loops -fstack-protector -march=pentium3 -mfpmath=sse -mmmx -msse -I./../include -D_GNU_SOURCE -DCONFIG_ROOT_CHECK_OFF=0 -DELF_MACHINE_H='"elf_i386.h"' -DARCH_i386 -DTAINT_URL='"http://www.tux.org/lkml/#export-tainted"' -DCOMBINE_rmmod -DCOMBINE_modprobe -DCOMBINE_lsmod -DCOMBINE_ksyms -DCOMBINE_kallsyms -Dmain=combined_insmod_main -c -o combined_insmod.o insmod.c ar rv libmodutils.a ksyms.o a - ksyms.o ar rv libmodutils.a kallsyms.o a - kallsyms.o ar rv libmodutils.a lsmod.o a - lsmod.o gcc -O2 -fomit-frame-pointer -funroll-loops -fstack-protector -march=pentium3 -mfpmath=sse -mmmx -msse -o modinfo modinfo.o ../obj/libobj.a ../util/libutil.a ar rv libmodutils.a rmmod.o a - rmmod.o gcc -O2 -fomit-frame-pointer -funroll-loops -fstack-protector -march=pentium3 -mfpmath=sse -mmmx -msse -o insmod insmod.o rmmod.o modprobe.o lsmod.o ksyms.o kallsyms.o ../obj/libobj.a ../util/libutil.a gcc -static -O2 -fomit-frame-pointer -funroll-loops -fstack-protector -march=pentium3 -mfpmath=sse -mmmx -msse -o insmod.static insmod.o rmmod.o modprobe.o lsmod.o ksyms.o kallsyms.o ../obj/libobj.a ../util/libutil.a ar rv libmodutils.a modprobe.o a - modprobe.o ln -sf insmod modprobe ln -sf insmod rmmod ln -sf insmod lsmod ln -sf insmod ksyms ln -sf insmod kallsyms ar rv libmodutils.a combined_insmod.o a - combined_insmod.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../../libc.a(ssp.o)(.data+0x0): multiple definition of `__guard' /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libgcc.a(_stack_smash_handler.oS)(.data+0x0):/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/gcc/libgcc2.c:2078: first defined here /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../../libc.a(ssp.o)(.text+0x80): In function `__stack_smash_handler': : multiple definition of `__stack_smash_handler' /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libgcc.a(_stack_smash_handler.oS)(.text+0x90):/var/tmp/portage/gcc-3.2.3-r2/work/gcc-3.2.3/gcc/libgcc2.c:2093: first defined here /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../../../i686-pc-linux-gnu/bin/ld: Warning: size of symbol `__stack_smash_handler' changed from 722 in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libgcc.a(_stack_smash_handler.oS) to 577 in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libgcc.a(_stack_smash_handler.oS) collect2: ld returned 1 exit status distcc[4282] ERROR: compile on localhost failed make[1]: *** [insmod.static] Error 1 make[1]: Leaving directory `/var/tmp/portage/modutils-2.4.25/work/modutils-2.4.25/insmod' make: *** [all] Error 2 !!! ERROR: sys-apps/modutils-2.4.25 failed. !!! Function src_compile, Line 42, Exitcode 2 !!! emake failed To me, that looks like a possible GCC / Glibc bug as the duplicate-symbols are inside GCC / Glibc. Are you using gcc-3.2.3-r3? Otherwise, -static and -fstack-protector are broken and will fail. Please see bug #25299 for more information. No, I am still using 3.2.3-r2. It was up-to-date 2 days before when I emerged the portage tree... :-/ OK, I just started an "emerge -Du world". New gcc, new kernel... man! ;-) The next new setup I will start will be ~x86 right from the start... Perhaps then my bugreports will notify you of not-already-solved problems. ;-) --- Hey, if I understand this ebuild correct I shall recompile all my packages which were compiled with -fstack-protector?? I just started the find and it spits out quite a lot packages which were compiled without errors... Help ;-) |
