From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issues with the toolchain wrapper applied to the internal toolchain
Date: Wed, 14 Oct 2015 10:58:28 +0200 [thread overview]
Message-ID: <20151014105828.54391fb9@free-electrons.com> (raw)
In-Reply-To: <561AC198.9070206@mind.be>
Arnout,
On Sun, 11 Oct 2015 22:07:52 +0200, Arnout Vandecappelle wrote:
> One solution for both issues would be to deal with buildroot-built toolchains
> explicitly in the toolchain wrapper, i.e. detect the existence of .real and exec
> that one directly. Would that be an acceptable solution?
I think there are other situations where a .real file could exist, for
example for FLAT toolchains, there is often a wrapper that will call
elf2flt, and the real compiler is also called <something>.real, if I
remember correctly.
So maybe we need to adjust this to .buildroot-real or something that is
less likely to cause any sort of mis-detection?
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 8:58 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 [this message]
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
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=20151014105828.54391fb9@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