Summary: | glibc can be built only if -U_FORTIFY_SOURCE is added to CFLAGS | ||
---|---|---|---|
Product: | glibc | Reporter: | booleandomain |
Component: | build | Assignee: | Carlos O'Donell <carlos> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | carlos, dick, glibc-bugs, jrnieder, jyasskin, roland, sapiensantiquus, toolchain, zorry |
Priority: | P2 | Flags: | fweimer:
security-
|
Version: | 2.10 | ||
Target Milestone: | 2.16 | ||
See Also: | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46596 | ||
Host: | x86_64-pc-linux-gnu | Target: | x86_64-pc-linux-gnu |
Build: | x86_64-pc-linux-gnu | Last reconfirmed: | 2012-02-29 00:00:00 |
Description
booleandomain
2009-07-07 19:16:55 UTC
*** This bug has been marked as a duplicate of 333 *** This looks like http://gcc.gnu.org/PR46596. I can confirm this. My build scripts all have -U_FORTIFY_SOURCE in CFLAGS. I'll have a look at fixing this. *** Bug 11180 has been marked as a duplicate of this bug. *** Confirmed here as well. Note compilers (like Debian/Ubuntu) that predefine _FORTIFY_SOURCE also implicitly set -fstack-protector, which I think is also a problem for building libc. (In reply to comment #6) > Note compilers (like Debian/Ubuntu) that predefine _FORTIFY_SOURCE also > implicitly set -fstack-protector, which I think is also a problem for building > libc. To avoid confusion: Debian gcc does not predefine _FORTIFY_SOURCE or implicitly set -fstack-protector. Ubuntu gcc does, though. Fixed in trunk. *** Bug 260998 has been marked as a duplicate of this bug. *** Seen from the domain http://volichat.com Page where seen: http://volichat.com/adult-chat-rooms Marked for reference. Resolved as fixed @bugzilla. |