From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: control GNU_TARGET_NAME vendor part
Date: Mon, 3 Mar 2014 22:24:00 +0100 [thread overview]
Message-ID: <20140303212359.GG3380@free.fr> (raw)
In-Reply-To: <884EA965490E3C4D8E66AEF41E98025006C816@ezex10.ezchip.com>
Noam, All,
On 2014-02-23 15:41 +0000, Noam Camus spake thusly:
[--SNIP--]
> Below is the revised patch.
> Is it OK?
> Is it the right way to bring up the corrections?
Please just re-send the patch as you did the first time.
Be sure to annotate it as:
[PATCH v2] blabla
You can do that with:
git send-email --annotate [...]
[--SNIP--]
> diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in
> index cd88889..216f308 100644
> --- a/toolchain/toolchain-buildroot/Config.in
> +++ b/toolchain/toolchain-buildroot/Config.in
> @@ -69,6 +69,18 @@ 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 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.
I think Thomas said on IRC that he will have a better wording for the
help text. Wait a little bit for his suggestion, before re-sending.
Thanks!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-03-03 21:24 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 [this message]
2014-03-03 21:44 ` Thomas Petazzoni
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=20140303212359.GG3380@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