From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain-external: bypass buildroot wrapper
Date: Wed, 14 Oct 2015 23:31:06 +0200 [thread overview]
Message-ID: <20151014233106.416d10e6@free-electrons.com> (raw)
In-Reply-To: <1444856755-2011-2-git-send-email-arnout@mind.be>
Arnout,
On Wed, 14 Oct 2015 23:05:55 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> Lightly tested with an internal toolchain, an external Sourcery
> toolchain, an external downloaded buildroot toolchain, and an external
> pre-installed buildroot toolchain.
Did you test with a pre-existing Buildroot toolchain (i.e that predates
the introduction of the wrapper for internal toolchain), or did you
build a Buildroot toolchain with the latest Buildroot (including your
patches) and then re-used it as an external toolchain in another
Buildroot configuration ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-14 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 10:08 [Buildroot] Issues with the toolchain wrapper applied to the internal toolchain Thomas Petazzoni
2015-10-11 20:07 ` Arnout Vandecappelle
2015-10-14 8:56 ` Arnout Vandecappelle
2015-10-14 10:46 ` Peter Korsgaard
2015-10-14 8:58 ` Thomas Petazzoni
2015-10-14 9:20 ` Arnout Vandecappelle
2015-10-14 21:05 ` [Buildroot] [PATCH 1/2] gcc: use '.br_real' instead of '.real' for the wrapped toolchain Arnout Vandecappelle
2015-10-14 21:05 ` [Buildroot] [PATCH 2/2] toolchain-external: bypass buildroot wrapper Arnout Vandecappelle
2015-10-14 21:31 ` Thomas Petazzoni [this message]
2015-10-14 21:55 ` Arnout Vandecappelle
2015-10-17 8:52 ` Peter Korsgaard
2015-10-17 8:50 ` [Buildroot] [PATCH 1/2] gcc: use '.br_real' instead of '.real' for the wrapped toolchain 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=20151014233106.416d10e6@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