public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13979] A warning should be issued if FORTIFY_SOURCE is requested but not enabled
Date: Tue, 08 May 2012 17:49:00 -0000 [thread overview]
Message-ID: <bug-13979-131-fVRijbTUxL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13979-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13979
Andreas Jaeger <aj at suse dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |aj at suse dot de
Resolution| |FIXED
--- Comment #1 from Andreas Jaeger <aj at suse dot de> 2012-05-08 17:48:11 UTC ---
Thanks for your report and patch.
This is fixed slightly differently for glibc 2.16 with:
commit 05c2c9618f583ea4acd69b3fe5ae2a2922dd2ddc
Author: Roland Mc Grath <roland@hack.frob.com>
Date: Tue May 8 19:44:57 2012 +0200
Warn if user requests __FORTIFY_SOURCE but it is disabled
[BZ #13979]
* include/features.h: Warn if user requests __FORTIFY_SOURCE
checking but the checks are disabled for any reason.
--
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-05-08 17:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 17:20 [Bug libc/13979] New: " law at redhat dot com
2012-05-07 21:05 ` [Bug libc/13979] " aj at suse dot de
2012-05-08 17:49 ` aj at suse dot de [this message]
2012-05-08 17:56 ` law at redhat dot com
2013-05-08 15:25 ` eblake at redhat dot com
2013-05-08 15:53 ` aj at suse dot de
2013-05-08 15:54 ` law at redhat dot com
2013-10-20 18:35 ` neleai at seznam dot cz
2014-06-25 11:17 ` fweimer at redhat dot com
2014-11-24 0:08 ` anatol.pomozov at gmail dot com
2014-11-24 6:31 ` fweimer at redhat dot com
2014-11-24 18:41 ` anatol.pomozov at gmail dot com
2014-11-24 18:46 ` fweimer at redhat dot com
2014-11-24 19:36 ` anatol.pomozov at gmail dot com
2023-08-07 9:41 ` sam at gentoo dot org
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-13979-131-fVRijbTUxL@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).