From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11616] 2018.02.09 fails to build libzlib with full RELRO protection
Date: Sat, 12 Jan 2019 13:59:11 +0000 [thread overview]
Message-ID: <bug-11616-163-CVWQdkd4YZ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11616-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11616
--- Comment #5 from Matt Weber <matthew.weber@rockwellcollins.com> ---
Tho(In reply to Thomas Petazzoni from comment #4)
Oh right. So then for this failure case it is a known issue that the ordering
of linker steps in most packages are not correct to support RELRO full. Which
is what lead to using the toolchain wrapper to adjust ordering as the current
solution.
Karl, are you able to bump versions to 2018.11 or next month to the new LTS?
If not I can help you find the series of commits to add to your LTS that enable
the toolchain wrapper method, however you'd have to carry your own LTS branch
locally for this to work.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-01-12 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 7:39 [Buildroot] [Bug 11616] New: 2018.02.09 fails to build libzlib with full RELRO protection bugzilla at busybox.net
2019-01-11 7:44 ` [Buildroot] [Bug 11616] " bugzilla at busybox.net
2019-01-11 7:45 ` bugzilla at busybox.net
2019-01-11 7:46 ` bugzilla at busybox.net
2019-01-11 14:16 ` bugzilla at busybox.net
2019-01-12 9:21 ` bugzilla at busybox.net
2019-01-12 13:59 ` bugzilla at busybox.net [this message]
2019-01-14 7:49 ` bugzilla at busybox.net
2019-01-14 14:06 ` bugzilla at busybox.net
2019-01-14 21:33 ` bugzilla at busybox.net
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-11616-163-CVWQdkd4YZ@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