From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: control GNU_TARGET_NAME vendor part
Date: Mon, 3 Mar 2014 22:44:41 +0100 [thread overview]
Message-ID: <20140303224441.546bf9f3@skate> (raw)
In-Reply-To: <884EA965490E3C4D8E66AEF41E98025006C816@ezex10.ezchip.com>
Dear Noam Camus,
On Sun, 23 Feb 2014 15:41:43 +0000, Noam Camus wrote:
> +config BR2_TOOLCHAIN_BUILDROOT_VENDOR
> + string "custom toolchain vendor name"
> + default "buildroot"
> + help
> + This option accepts name for vendor field in toolchain tuple.
> + The toolchain tuple full format is:
> + cpu-vendor-kernel-os
> + You may use it in case of custom toolchain.
> + e.g. if your gcc depend on this field to make decisions.
> + NOTE: "unknown" is not allowed since it may be confused
> + with host toolchain.
A better wording IMO:
This option allows to customize the "vendor" part of the
toolchain tuple, where the toolchain tuple has the form
<cpu>-<vendor>-<kernel>-<os>. The default value, "buildroot",
is fine for most cases, except in very specific situations
where gcc might make different decisions based on the vendor
part of the tuple. The value "unknown" is not allowed as the
cross-compiling toolchain might then be confused with the
native toolchain when the target and host architecture are
identical.
If you're not sure, just leave the default "buildroot" value.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-03 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 8:28 [Buildroot] [PATCH] toolchain: control GNU_TARGET_NAME vendor part Noam Camus
2014-02-23 9:46 ` Thomas Petazzoni
2014-02-23 11:45 ` Noam Camus
2014-02-23 11:51 ` Thomas Petazzoni
2014-02-23 15:41 ` Noam Camus
2014-03-03 21:24 ` Yann E. MORIN
2014-03-03 21:44 ` Thomas Petazzoni [this message]
2014-03-04 3:47 ` Noam Camus
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=20140303224441.546bf9f3@skate \
--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