From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10491] Cannot output security warning when compiled with buildroot cross compilers
Date: Sat, 11 Nov 2017 09:18:48 +0000 [thread overview]
Message-ID: <bug-10491-163-czLFJ6DYiC@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10491-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10491
Arnout Vandecappelle <arnout@mind.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
The warning you are looking for is supposed to be triggered by
-D_FORTIFY_SOURCE=2.
Fortify is a bit special: it requires support both in the compiler and in libc.
GCC has this support since 4.0, but uClibc and musl don't have support for
Fortify at all. Thus, there is no way that -D_FORTIFY_SOURCE=2 is going to work
with uClibc.
When support for Fortify will land in core Buildroot, it will depend on a glibc
toolchain.
See also the discussion in http://patchwork.ozlabs.org/patch/830253/
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-11-11 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 6:56 [Buildroot] [Bug 10491] New: Cannot output security warning when compiled with buildroot cross compilers bugzilla at busybox.net
2017-11-11 9:18 ` bugzilla at busybox.net [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-10491-163-czLFJ6DYiC@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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