From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11206] zlib: fails to build with Linaro toolchain, BR2_RELRO_FULL=y and BR2_FORTIFY_SOURCE_2=y
Date: Fri, 02 Nov 2018 10:57:24 +0000 [thread overview]
Message-ID: <bug-11206-163-qsxmL5YQjL@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11206-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11206
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I believe this has been fixed by the changes to the toolchain wrapper to make
it handle the hardening options:
394bdd11fc1f741c88c89f0e71571d87a29ab627 BR2_FORTIFY*: toolchain wrapper
limitation note
f10822d151085bcbfecd0ecf2542ac5f5623fd9d toolchain/toolchain-wrapper: add
BR2_SSP_* support
7484c1c3b8065d6f2f5a67607e9917ecfea022eb toolchain/toolchain-wrapper: add
BR2_RELRO_
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-11-02 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:31 [Buildroot] [Bug 11206] New: zlib: fails to build with Linaro toolchain, BR2_RELRO_FULL=y and BR2_FORTIFY_SOURCE_2=y bugzilla at busybox.net
2018-08-07 17:32 ` [Buildroot] [Bug 11206] " bugzilla at busybox.net
2018-08-07 18:31 ` bugzilla at busybox.net
2018-08-07 18:32 ` bugzilla at busybox.net
2018-09-13 2:40 ` bugzilla at busybox.net
2018-11-02 10:57 ` 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-11206-163-qsxmL5YQjL@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.