From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/5] toolchain/toolchain-wrapper: add link wrapper
Date: Thu, 30 Aug 2018 09:53:49 +0200 [thread overview]
Message-ID: <20180830095349.1247fe54@windsurf> (raw)
In-Reply-To: <1535600085-31526-2-git-send-email-matthew.weber@rockwellcollins.com>
Hello Matt,
On Wed, 29 Aug 2018 22:34:41 -0500, Matt Weber wrote:
> - Updates symlink creation int/ext toolchain
> - Adds new source file for link wrapper with build/install
>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
I think this commit log should contain a detailed explanation of why
wrapping the linker is necessary. Could you provide an example of a
package that absolutely needs the linker to be wrapped ? I'd like to do
a bit of testing, because I'm still not entirely convinced that we want
to wrap the linker. Perhaps we need to do this, but I'd like to spend a
bit of time looking at a specific example of a package that makes this
necessary. Could you provide such an example ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-30 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 3:34 [Buildroot] [PATCH v2 0/5] Hardening Wrapper Updates and Test Matt Weber
2018-08-30 3:34 ` [Buildroot] [PATCH v2 1/5] toolchain/toolchain-wrapper: add link wrapper Matt Weber
2018-08-30 7:53 ` Thomas Petazzoni [this message]
2018-08-30 12:48 ` Matthew Weber
2018-08-30 3:34 ` [Buildroot] [PATCH v2 2/5] toolchain/toolchain-wrapper: add BR2_RELRO_FULL support Matt Weber
2018-08-30 3:34 ` [Buildroot] [PATCH v2 3/5] toolchain/toolchain-wrapper: add BR2_SSP_* support Matt Weber
2018-08-30 3:34 ` [Buildroot] [PATCH v2 4/5] toolchain/toolchain-wrapper: add BR2_FORTIFY_SOURCE_* support Matt Weber
2018-08-30 3:34 ` [Buildroot] [PATCH v2 5/5] support/testing/tests/core: SSP & hardening flags Matt Weber
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=20180830095349.1247fe54@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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