From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-wrapper: fix breakage after host/usr removal
Date: Fri, 7 Jul 2017 13:58:23 +0200 [thread overview]
Message-ID: <20170707135823.032c25d6@windsurf.lan> (raw)
In-Reply-To: <20170707074330.27294-1-arnout@mind.be>
Hello,
On Fri, 7 Jul 2017 09:43:30 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> The toolchain wrapper, when called through PATH, strips the last three
> levels of /proc/self/exe to find HOST_DIR. However, after the host/usr
> removal, this should be just two levels.
>
> The toolchain wrapper has different logic for when it is called with a
> full path (i.e. $HOST_DIR/usr/bin/arm-linux-gcc) then when it is called
> through the PATH (i.e. just arm-linux-gcc). The latter is never used
> internally in Buildroot, that's why this wasn't discovered through
> testing.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Mark Jackson <mpfj-list@newflow.co.uk>
> ---
> Sorry for the breakage :-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-07 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 14:34 [Buildroot] ARM cross compiler path error "no such file or directory" Mark Jackson
2017-07-06 15:35 ` Thomas Petazzoni
2017-07-06 21:50 ` Arnout Vandecappelle
2017-07-07 7:24 ` Thomas Petazzoni
2017-07-07 7:43 ` [Buildroot] [PATCH] toolchain-wrapper: fix breakage after host/usr removal Arnout Vandecappelle
2017-07-07 11:12 ` Mark Jackson
2017-07-07 11:58 ` Thomas Petazzoni [this message]
2017-07-08 14:08 ` [Buildroot] ARM cross compiler path error "no such file or directory" Marcus Hoffmann
2017-07-08 15:20 ` Arnout Vandecappelle
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=20170707135823.032c25d6@windsurf.lan \
--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