From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-22
Date: Wed, 28 May 2014 09:06:39 +0200 [thread overview]
Message-ID: <20140528090639.732647c8@free-electrons.com> (raw)
In-Reply-To: <20140528064706.GC3510@free.fr>
Dear Yann E. MORIN,
On Wed, 28 May 2014 08:47:06 +0200, Yann E. MORIN wrote:
> > > Yes, I think this is a good idea. But we can't use the wrapper to build
> > > the toolchain itself, of course.
> >
> > And there is no wrapper at all when we use the internal toolchain
> > backend. At least as of today.
>
> Hu? Of course we're not using the wrapper for internal toolchain. That's
> why I replied it would be a good idea to use it (OK, I should have
> trimmed the quote a bit more.)
Regarding using the wrapper for the internal toolchain, there's always
the problem of where we put the real toolchain binaries vs. the wrapper
binaries. For the external toolchain, it's simple: the real toolchain
binaries are in $(HOST_DIR)/opt/ext-toolchain, and the wrappers in
$(HOST_DIR)/usr/bin. But for the internal toolchain, we build/install
all the toolchain components with --prefix=$(HOST_DIR)/usr.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-28 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-22 Thomas Petazzoni
2014-05-23 9:32 ` Fabio Porcedda
2014-05-23 17:08 ` Thomas Petazzoni
2014-05-28 6:10 ` Arnout Vandecappelle
2014-05-28 6:30 ` Yann E. MORIN
2014-05-28 6:43 ` Thomas Petazzoni
2014-05-28 6:47 ` Yann E. MORIN
2014-05-28 7:06 ` Thomas Petazzoni [this message]
2014-05-28 8:05 ` 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=20140528090639.732647c8@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