From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] [V6] toolchain: control vendor part in GNU_TARGET_NAME
Date: Mon, 31 Mar 2014 18:59:49 +0200 [thread overview]
Message-ID: <20140331165949.GA5004@free.fr> (raw)
In-Reply-To: <884EA965490E3C4D8E66AEF41E9802500AA064@ezex10.ezchip.com>
Noam, All,
On 2014-03-09 07:15 +0000, Noam Camus spake thusly:
>
> 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.
>
> Signed-off-by: Noam Camus <noamc@ezchip.com>
Small nit below...
> ---
> package/Makefile.in | 17 ++++++++++++++++-
> toolchain/toolchain-buildroot/Config.in | 16 ++++++++++++++++
> 2 files changed, 32 insertions(+), 1 deletions(-)
>
> diff --git a/package/Makefile.in b/package/Makefile.in
> index 454f614..bd9f18c 100644
> --- a/package/Makefile.in
> +++ b/package/Makefile.in
> @@ -20,8 +20,23 @@ endif
> MAKE1:=$(HOSTMAKE) -j1
> MAKE:=$(HOSTMAKE) $(if $(PARALLEL_JOBS),-j$(PARALLEL_JOBS))
>
> +ifeq ($(BR2_TOOLCHAIN_BUILDROOT),y)
> +TARGET_VENDOR = $(call qstrip,$(BR2_TOOLCHAIN_BUILDROOT_VENDOR))
> +else
> +TARGET_VENDOR = buildroot
> +endif
> +
> +# Sanity checks
> +ifeq ($(TARGET_VENDOR),)
> +$(error BR2_TOOLCHAIN_BUILDROOT_VENDOR is not allowed to be empty)
> +endif
> +ifeq ($(TARGET_VENDOR),unknown)
> +$(error BR2_TOOLCHAIN_BUILDROOT_VENDOR cannot be 'unknown'. \
> + It might be confused with the native toolchain)
> +endif
> +
> # Compute GNU_TARGET_NAME
> -GNU_TARGET_NAME=$(ARCH)-buildroot-$(TARGET_OS)-$(LIBC)$(ABI)
> +GNU_TARGET_NAME=$(ARCH)-$(TARGET_VENDOR)-$(TARGET_OS)-$(LIBC)$(ABI)
>
> # Blackfin FLAT needs uclinux
> ifeq ($(BR2_bfin)$(BR2_BINFMT_FLAT),yy)
> diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in
> index 07db50b..3487327 100644
> --- a/toolchain/toolchain-buildroot/Config.in
> +++ b/toolchain/toolchain-buildroot/Config.in
> @@ -70,6 +70,22 @@ config BR2_TOOLCHAIN_BUILDROOT_LIBC
> default "glibc" if BR2_TOOLCHAIN_BUILDROOT_EGLIBC
> default "glibc" if BR2_TOOLCHAIN_BUILDROOT_GLIBC
>
> +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.
This can not be empty either.
With that added:
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> + If you're not sure, just leave the default "buildroot" value.
> +
> source "package/uclibc/Config.in"
> source "package/glibc/Config.in"
> source "package/binutils/Config.in.host"
> --
> 1.7.1
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-03-31 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 7:15 [Buildroot] [PATCH 1/1] [V6] toolchain: control vendor part in GNU_TARGET_NAME Noam Camus
2014-03-31 16:59 ` Yann E. MORIN [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=20140331165949.GA5004@free.fr \
--to=yann.morin.1998@free.fr \
--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