All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexey Brodkin via buildroot <buildroot@buildroot.org>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Subject: Re: [Buildroot] [PATCH] package/binutils: ARC: Re-add poison system directories patch
Date: Wed, 10 Jan 2024 21:38:26 +0100	[thread overview]
Message-ID: <20240110213826.576052c7@windsurf> (raw)
In-Reply-To: <20240105180422.424279-1-abrodkin@synopsys.com>

On Fri,  5 Jan 2024 10:04:22 -0800
Alexey Brodkin via buildroot <buildroot@buildroot.org> wrote:

> While updating ARC GNU toolchain version (see [1]) we unintentionally
> got rid of "0001-poison-system-directories.patch" which still makes
> sense.
> 
> Even though one may think that we do not need these Binutils patches
> because we do "poisoning" of system directories in toolchain wrapper,
> but these wrappers don't exist for tools originated from Binutils, only
> for gcc, g++ etc.
> 
> So we need to keep that patch still, sorry.
> 
> [1] https://git.buildroot.net/buildroot/commit/?id=045ab73702b8bc09f94ca1f3b8e5bf3acb0b0843
> 
> Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> ---
>  .../0001-poison-system-directories.patch      | 309 ++++++++++++++++++
>  1 file changed, 309 insertions(+)
>  create mode 100644 package/binutils/arc-2023.09-release/0001-poison-system-directories.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-01-10 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 18:04 [Buildroot] [PATCH] package/binutils: ARC: Re-add poison system directories patch Alexey Brodkin via buildroot
2024-01-10 20:38 ` Thomas Petazzoni via buildroot [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=20240110213826.576052c7@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.