All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 14 Jan 2019 14:06:47 +0000	[thread overview]
Message-ID: <bug-11616-163-x3MzpmilVe@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 #7 from Matt Weber <matthew.weber@rockwellcollins.com> ---
If you did need to do full RELRO, you could pull the following commits in on
your LTS to change the toolchain-wrapper behavior.

git cherry-pick d4f5801027f3329fb6c2cd096f3396d3cd067390 
01d8a0a9455f9408819d7f135fba5139f0672507
7484c1c3b8065d6f2f5a67607e9917ecfea022eb
f10822d151085bcbfecd0ecf2542ac5f5623fd9d 


Care to mark this one closed?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-01-14 14:06 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
2019-01-14  7:49 ` bugzilla at busybox.net
2019-01-14 14:06 ` bugzilla at busybox.net [this message]
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-x3MzpmilVe@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.