From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] gcc: use '.br_real' instead of '.real' for the wrapped toolchain
Date: Sat, 17 Oct 2015 10:50:12 +0200 [thread overview]
Message-ID: <876125281n.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1444856755-2011-1-git-send-email-arnout@mind.be> (Arnout Vandecappelle's message of "Wed, 14 Oct 2015 23:05:54 +0200")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
I find the subject quite hard to understand. The .real / .br_real is
not for the WRAPPED toolchain, but for the RAW toolchain binaries.
> If an externally built toolchain also wraps the toolchain executables,
> there is a risk that it will also use the '.real' extension. To
> minimise this risk, use a more buildroot-specific extension instead:
> '.br_real'.
> For the time being, this is not yet a problem since the internal
> toolchain never has such a wrapper. However, in a later commit we
> will bypass the buildroot wrapper for external toolchains, so we
> have to avoid doing that when it's not buildroot that wrapped it.
I'm not sure what you mean here. We DO have a a wrapper for the internal
toolchain.
Committed with the description reworded, thanks!
--
Venlig hilsen,
Peter Korsgaard
prev parent reply other threads:[~2015-10-17 8:50 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
2015-10-14 21:55 ` Arnout Vandecappelle
2015-10-17 8:52 ` Peter Korsgaard
2015-10-17 8:50 ` Peter Korsgaard [this message]
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=876125281n.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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