Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Matthew McClintock <msm@freescale.com>
Subject: Re: [PATCH] Remove EGLIBPARALLELISM from deps for EXTRA_OEMAKE
Date: Tue, 22 Nov 2011 11:50:46 -0800	[thread overview]
Message-ID: <4ECBFD16.3020406@linux.intel.com> (raw)
In-Reply-To: <1321568900-19406-1-git-send-email-msm@freescale.com>

On 11/17/2011 02:28 PM, Matthew McClintock wrote:
> Without this simply changing the number of threads via
> PARALLEL_MAKE can invalidate sstate-cache
>
> Signed-off-by: Matthew McClintock<msm@freescale.com>
> ---
>   meta/recipes-core/eglibc/eglibc.inc |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-core/eglibc/eglibc.inc b/meta/recipes-core/eglibc/eglibc.inc
> index fe9f8ba..272fcb6 100644
> --- a/meta/recipes-core/eglibc/eglibc.inc
> +++ b/meta/recipes-core/eglibc/eglibc.inc
> @@ -40,6 +40,7 @@ ARM_INSTRUCTION_SET = "arm"
>   # eglibc uses PARALLELMFLAGS variable to pass parallel build info so transfer
>   # PARALLEL_MAKE into PARALLELMFLAGS and empty out PARALLEL_MAKE
>   EGLIBCPARALLELISM := "PARALLELMFLAGS="${PARALLEL_MAKE}""
> +EXTRA_OEMAKE[vardepsexclude] += "EGLIBCPARALLELISM"
>   EXTRA_OEMAKE += ${EGLIBCPARALLELISM}
>   PARALLEL_MAKE = ""
>

When possible, please include the recipe or file you are changing as 
part of the patch subject.

For example this would be:

eglibc.inc: Remove EGLIBPARALLELISM from deps for EXTRA_OEMAKE

Thanks
	Sau!



  reply	other threads:[~2011-11-22 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 22:28 [PATCH] Remove EGLIBPARALLELISM from deps for EXTRA_OEMAKE Matthew McClintock
2011-11-22 19:50 ` Saul Wold [this message]
2011-11-22 22:40   ` McClintock Matthew-B29882
2011-11-22 22:49     ` Saul Wold
2011-11-24 22:53       ` Richard Purdie

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=4ECBFD16.3020406@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=msm@freescale.com \
    --cc=openembedded-core@lists.openembedded.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