public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/31928] glibc doesn't compile if the compiler already define _FORTIFY_SOURCE Date: Wed, 26 Jun 2024 19:17:36 +0000 [thread overview] Message-ID: <bug-31928-131-LqoDmz5YWe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31928-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31928 --- Comment #5 from Florian Weimer <fweimer at redhat dot com> --- If -U works, we can switch to that. The use of -Wp goes back to CFLAGS settings which needed to be compatible with GCJ, where -D had a different meaning. Hence, -Wp,-D_FORTIFY_SOURCE=2 came into being, and it has been carried forward ever since. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-06-26 19:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-25 15:06 [Bug build/31928] New: " simon.chopin at canonical dot com 2024-06-26 7:14 ` [Bug build/31928] " fweimer at redhat dot com 2024-06-26 7:48 ` sam at gentoo dot org 2024-06-26 8:30 ` simon.chopin at canonical dot com 2024-06-26 8:36 ` fweimer at redhat dot com 2024-06-26 11:48 ` adhemerval.zanella at linaro dot org 2024-06-26 19:17 ` fweimer at redhat dot com [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31928-131-LqoDmz5YWe@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).