Summary: | libc-2.3.5-r3 won't build --> undefined reference to '.LC3' (in csu/crtn.S) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jamie Saker <jsaker> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jamie Saker
2005-11-26 07:12:46 UTC
*** This bug has been marked as a duplicate of 111217 *** Jamie - remove '-fstack-protector-all' from CFLAGS in make.conf You really don't want it there, the hardened compiler will make a much better guess at when it's ok to switch that on for you. Thanks Kevin - will remove it and procede. I'm assuming the USE=hardened will guide my installs to add the flag when it can? No; the use flag won't do it for other ebuilds, but the compiler you built with USE=hardened will. The hardened compiler automagically switch on SSP when compiling regardless of your use flags. USE=hardened is used (1) by the gcc build to create and use the hardened compiler by default and (2) by other ebuilds to conditionally fix stuff that breaks either as a result of using the hardened compiler, or as a result of the kernel hardening from PaX & grsecurity. The default with a normal compiler is to build without SSP - with the hardened compiler, the default is to build _with_ SSP except for some known situations in which it can't work, where this can be detected automatically. FWIW one other thing the hardened compiler does, is to automatically "upgrade" -fstack-protector to -fstack-protector-all. |