From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 1/1] ncurses: Disable parallel make
Date: Wed, 16 May 2012 14:02:57 +0300 [thread overview]
Message-ID: <4FB38961.2000702@linux.intel.com> (raw)
In-Reply-To: <a918712a769df875f9e59f7a5aa233b7316705c2.1337162056.git.xiaofeng.yan@windriver.com>
On 05/16/2012 01:10 PM, xiaofeng.yan@windriver.com wrote:
> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>
> Ncurses failure non-gplv3 build by race issue. So disable parallel \
> make when building this package.
>
This is not the best approach as you disable PARALLEL_MAKE for both
non-gplv3 and gplv3 versions. Further, we want to get rid of
PARALLLEL_MAKE setting as much as possible, so this patch is not helping
that.
Did you try running on a large many core machine? It might help if you
have some other builds going also to stress the machine.
Sau!
> Signed-off-by: Xiaofeng Yan<xiaofeng.yan@windriver.com>
> ---
> meta/recipes-core/ncurses/ncurses.inc | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-core/ncurses/ncurses.inc
> index ae99e2c..b115e46 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -29,6 +29,8 @@ BUILD_CPPFLAGS += "-D_GNU_SOURCE"
> # natives don't generally look in base_libdir
> base_libdir_virtclass-native = "${libdir}"
>
> +PARALLEL_MAKE = ""
> +
> # Helper function for do_configure to allow multiple configurations
> # $1 the directory to run configure in
> # $@ the arguments to pass to configure
next prev parent reply other threads:[~2012-05-16 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 10:10 [PATCH 0/1] ncurses: Disable parallel make xiaofeng.yan
2012-05-16 10:10 ` [PATCH 1/1] " xiaofeng.yan
2012-05-16 11:02 ` Saul Wold [this message]
2012-05-17 2:01 ` Xiaofeng Yan
2012-05-17 3:07 ` Khem Raj
2012-05-17 12:02 ` Jason Wessel
2012-05-18 3:25 ` Xiaofeng Yan
2012-05-18 7:33 ` Xiaofeng Yan
2012-05-18 12:14 ` Robert Yang
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=4FB38961.2000702@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Zhenfeng.Zhao@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.