From: Henning Heinold <heinold@inf.fu-berlin.de>
To: Phil Blundell <philb@gnu.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-configure-cross: factor out --enable-threads argument into ${GCCTHREADS}
Date: Wed, 26 Sep 2012 12:46:08 +0200 [thread overview]
Message-ID: <20120926104608.GA23994@mi.fu-berlin.de> (raw)
In-Reply-To: <1348652719.31293.90.camel@phil-desktop>
On Wed, Sep 26, 2012 at 10:45:18AM +0100, Phil Blundell wrote:
> This allows BSPs for architectures with no thread support to set (for
> example) "GCCTHREADS=no" without having to override all the other configure
> parameters.
>
> Signed-off-by: Phil Blundell <pb@pbcl.net>
> ---
> meta/recipes-devtools/gcc/gcc-configure-common.inc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> index 908ad3e..504bfaa 100644
> --- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
> +++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
> @@ -26,12 +26,13 @@ EXTRA_OECONF_INITIAL ?= ""
> EXTRA_OECONF_INTERMEDIATE ?= ""
>
> GCCMULTILIB = "--disable-multilib"
> +GCCTHREADS = "posix"
Hi Phil,
should that not be GCCTHREADS ?=
otherwise I do not see how it could be overwritten from outside.
Bye Henning
next prev parent reply other threads:[~2012-09-26 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 9:45 [PATCH] gcc-configure-cross: factor out --enable-threads argument into ${GCCTHREADS} Phil Blundell
2012-09-26 9:54 ` Martin Jansa
2012-09-26 9:57 ` Phil Blundell
2012-09-26 10:01 ` Martin Jansa
2012-09-26 10:28 ` Phil Blundell
2012-09-26 13:46 ` Richard Purdie
2012-09-26 10:46 ` Henning Heinold [this message]
2012-09-26 10:50 ` Phil Blundell
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=20120926104608.GA23994@mi.fu-berlin.de \
--to=heinold@inf.fu-berlin.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.org \
/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