diff options
author | Noam Camus <noamc@ezchip.com> | 2014-04-01 06:25:47 +0000 |
---|---|---|
committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2014-04-06 14:16:06 +0200 |
commit | 65c2400ff251397db930e90c65c51d714d00fa96 (patch) | |
tree | 67f6ac6719052624876a1a02dcd9f8a9ff76536d /toolchain | |
parent | fb8774327ad06e8f59faf4da4ab40ffffd39d1dd (diff) | |
download | buildroot-65c2400ff251397db930e90c65c51d714d00fa96.tar.gz buildroot-65c2400ff251397db930e90c65c51d714d00fa96.zip |
toolchain: control vendor part in GNU_TARGET_NAME
This option allows to customize the "vendor" part of the
toolchain tuple, where the toolchain tuple has the form
<arch>-<vendor>-<os>-<libc>. Use this option in situations
where gcc might make different decisions based on the vendor
part of the tuple.
[Thomas: move the config option in a slightly different place, so that
it does not appear between the C library selection and the C library
options.]
Signed-off-by: "Noam Camus" <noamc@ezchip.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'toolchain')
-rw-r--r-- | toolchain/toolchain-buildroot/Config.in | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in index 07db50bfcb..42166d2633 100644 --- a/toolchain/toolchain-buildroot/Config.in +++ b/toolchain/toolchain-buildroot/Config.in @@ -1,6 +1,23 @@ # Config entries for internal toolchain backend if BR2_TOOLCHAIN_BUILDROOT + +config BR2_TOOLCHAIN_BUILDROOT_VENDOR + string "custom toolchain vendor name" + default "buildroot" + help + This option allows to customize the "vendor" part of the + toolchain tuple, where the toolchain tuple has the form + <arch>-<vendor>-<os>-<libc>. 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. The value can not be empty either. + + If you're not sure, just leave the default "buildroot" value. + source "package/linux-headers/Config.in.host" choice |