From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with toolchain wrapper changes
Date: Wed, 17 Feb 2016 12:56:58 +0100 [thread overview]
Message-ID: <20160217125658.7776ac38@free-electrons.com> (raw)
In-Reply-To: <87lh6j1ttt.fsf@dell.be.48ers.dk>
Hello,
On Wed, 17 Feb 2016 12:04:30 +0100, Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> > Hello Arnout,
> > I am facing some issues with the toolchain wrapper, which I believe
> > were introduced by the changes done to use the toolchain wrapper also
> > for the internal toolchain backend.
>
> > As you know, Buildroot installs all its host stuff in $(HOST_DIR)/usr,
> > and not directly under $(HOST_DIR). For the autobuilders, I build a
> > number of toolchains with Buildroot, which are then used as pre-built
> > external toolchains by the autobuilders. In order for those toolchains
> > to look like conventional toolchains, at the end of their build, I do:
>
> > mv /path/to/host/usr/* /path/to/host/
> > rmdir /path/to/host/usr/
>
> > Which moves everything outside of the usr/ subdirectory, and removes
> > the usr/ subdirectory itself. This used to work perfectly fine, but
> > now, it fails to find the .br_real equivalent of the command being
> > executed. Example:
>
> Is the extra /usr really such a problem? I've built a bunch of
> toolchains, and just refer to them as /opt/br/<whatever>/usr.
Yes, for my purpose it's annoying. I want to produce pre-built
toolchains that everyone can use, in Buildroot or something else, so I
want them to look like normal toolchains. And normal toolchains don't
have this useless usr/ top-level directory.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-17 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 15:31 [Buildroot] Issue with toolchain wrapper changes Thomas Petazzoni
2016-02-13 20:37 ` Arnout Vandecappelle
2016-03-02 22:13 ` Thomas Petazzoni
2016-02-17 11:04 ` Peter Korsgaard
2016-02-17 11:56 ` Thomas Petazzoni [this message]
2016-02-17 17:23 ` Thomas De Schampheleire
2016-02-17 20:59 ` Thomas Petazzoni
2016-02-17 23:14 ` 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=20160217125658.7776ac38@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