public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at systemhalted dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug build/10375] glibc can be built only if -U_FORTIFY_SOURCE is added to CFLAGS
Date: Wed, 29 Feb 2012 13:59:00 -0000 [thread overview]
Message-ID: <bug-10375-131-wrIMqTqiAJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10375-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10375
Carlos O'Donell <carlos at systemhalted dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|DUPLICATE |
AssignedTo|drepper.fsp at gmail dot |carlos at systemhalted dot
|com |org
--- Comment #3 from Carlos O'Donell <carlos at systemhalted dot org> 2012-02-29 13:58:10 UTC ---
I can confirm this. My build scripts all have -U_FORTIFY_SOURCE in CFLAGS. I'll
have a look at fixing this.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-29 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10375-131@http.sourceware.org/bugzilla/>
2012-02-29 9:51 ` jyasskin at gmail dot com
2012-02-29 13:59 ` carlos at systemhalted dot org [this message]
2012-02-29 14:00 ` carlos at systemhalted dot org
2012-02-29 16:14 ` vapier at gentoo dot org
2012-03-08 3:28 ` carlos at systemhalted dot org
2012-04-24 20:18 ` sapiensantiquus at gmail dot com
2012-05-07 21:42 ` roland at gnu dot org
2012-05-14 4:57 ` jrnieder at gmail dot com
2012-05-16 23:26 ` roland at gnu dot org
2014-02-16 19:22 ` jackie.rosen at hushmail dot com
2014-05-28 19:44 ` schwab at sourceware dot org
2014-07-01 7:51 ` fweimer at redhat dot com
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-10375-131-wrIMqTqiAJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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: link
Be 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).