From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: improve poison system directory support
Date: Sun, 4 Oct 2015 15:51:27 +0100 [thread overview]
Message-ID: <20151004155127.4f116556@free-electrons.com> (raw)
In-Reply-To: <1432544520-665-1-git-send-email-vapier@gentoo.org>
Mike,
On Mon, 25 May 2015 05:02:00 -0400, Mike Frysinger wrote:
> From: Mike Frysinger <vapier@chromium.org>
>
> I've added support for the gold linker and reworked a bit the system:
> * The command line flags are always available.
> * The flag names are tweaked slightly to match existing flag standards.
> * We can turn on & off the warning via the command line.
> * The configure option controls the default warning behavior.
>
> This makes it easier for distros to take the patch and drop it into their
> setups. If they don't pass the configure flag, then it isn't enabled by
> default, and they get the same behavior w/out the patch. The difference
> is that people can still opt in to the warnings/errors via LDFLAGS.
>
> Signed-off-by: Mike Frysinger <vapier@chromium.org>
> ---
> .../2.25/600-poison-system-directories.patch | 254 +++++++++++++--------
> 1 file changed, 154 insertions(+), 100 deletions(-)
We are in fact going to drop our binutils/gcc poison detection patches,
since we are moving to generalizing the toolchain wrapper to be also
used in the internal toolchain case. Since the wrapper already does the
poisoning detection, there will no longer be a point to have such
gcc/binutils patches in Buildroot.
Consequently, I've marked your patch as Rejected in patchwork.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-04 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 9:02 [Buildroot] [PATCH] binutils: improve poison system directory support Mike Frysinger
2015-10-04 14:51 ` Thomas Petazzoni [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=20151004155127.4f116556@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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