From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sam-ba: use correct host arch binary for sam-ba symlink
Date: Sun, 25 Mar 2018 22:25:19 +0200 [thread overview]
Message-ID: <20180325222519.2d36d2f4@windsurf> (raw)
In-Reply-To: <1521735866-15288-1-git-send-email-joshua.henderson@microchip.com>
Hello Joshua,
On Thu, 22 Mar 2018 09:24:26 -0700, Joshua Henderson wrote:
> Make the symlink created in the host/bin directory point to the right host arch
> binary. This takes into account using the 32 bit or 64 bit binary.
>
> Signed-off-by: Joshua Henderson <joshua.henderson@microchip.com>
> ---
> package/sam-ba/sam-ba.mk | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
In fact, your commit does much more than fixing the sam-ba symlink
depending on the host architecture: the sam-ba symlink was *always*
broken. Indeed, you're changing this:
- ln -sf ../../opt/sam-ba/sam-ba $(HOST_DIR)/bin/sam-ba
+ ln -sf ../opt/sam-ba/$(SAM_BA_BIN_NAME) $(HOST_DIR)/bin/sam-ba
I.e you're removing one level of ../ when creating the relative
symlink. And this is needed since we moved $(HOST_DIR)/usr to
$(HOST_DIR).
So even on a x86 32 bit system, where the binary is named "sam-ba",
your commit fixes the symbolic link. I've reworded the commit log
accordingly, and applied your patch. Thanks!
Peter: this commit qualifies for 2018.02.x.
Joshua: what about updating to 2.17, or even Sam-ba 3.x ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-25 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 16:24 [Buildroot] [PATCH] sam-ba: use correct host arch binary for sam-ba symlink Joshua Henderson
2018-03-25 20:25 ` Thomas Petazzoni [this message]
2018-03-26 18:10 ` Joshua Henderson
2018-03-26 18:15 ` Thomas Petazzoni
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=20180325222519.2d36d2f4@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