Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: arc: fix custom patch
Date: Mon, 24 Apr 2017 16:21:54 +0300	[thread overview]
Message-ID: <1493040114-32538-1-git-send-email-vzakhar@synopsys.com> (raw)

This commit fixes another brown-paper-bag issue that I've introduced by
my following patch:
toolchain: Bump ARC tools to arc-2017.03-rc1
(5f8ef7e25c5cc5c2e4ae4c8b6e8caa029ddf9a94)

arc-2017.03-rc1 differs a bit from 2.28. And so corresponding
of-the-tree patch should be updated appropriately.

Fixes target binutils build for arc:
http://autobuild.buildroot.net/results/f67/f67c905979870936d8050a505b61186be6dad85d//

Signed-off-by: Vlad Zakharov <vzakhar@synopsys.com>
---
 .../binutils/arc-2017.03-rc1/0301-PATCH-check-ldrunpath-length.patch  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/binutils/arc-2017.03-rc1/0301-PATCH-check-ldrunpath-length.patch b/package/binutils/arc-2017.03-rc1/0301-PATCH-check-ldrunpath-length.patch
index f54b1b3..9bb2341 100644
--- a/package/binutils/arc-2017.03-rc1/0301-PATCH-check-ldrunpath-length.patch
+++ b/package/binutils/arc-2017.03-rc1/0301-PATCH-check-ldrunpath-length.patch
@@ -17,8 +17,8 @@ index d4837d0..937da8a 100644
  	      && command_line.rpath == NULL)
  	    {
  	      path = (const char *) getenv ("LD_RUN_PATH");
-+	      if ((lib_path) && (strlen (lib_path) == 0))
-+	        lib_path = NULL;
++	      if ((path) && (strlen (path) == 0))
++	        path = NULL;
  	      if (path
  		  && gld${EMULATION_NAME}_search_needed (path, &n, force))
  		break;
-- 
2.7.4

             reply	other threads:[~2017-04-24 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24 13:21 Vlad Zakharov [this message]
2017-04-24 20:33 ` [Buildroot] [PATCH] binutils: arc: fix custom patch Peter Korsgaard

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=1493040114-32538-1-git-send-email-vzakhar@synopsys.com \
    --to=vladislav.zakharov@synopsys.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