From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 1/1] gdk-pixbuf: fix parallel install issue
Date: Mon, 06 Aug 2012 13:55:25 +0100 [thread overview]
Message-ID: <1344257725.9756.147.camel@ted> (raw)
In-Reply-To: <1344205948.3541.2.camel@lenny>
On Sun, 2012-08-05 at 18:32 -0400, Colin Walters wrote:
> On Fri, 2012-08-03 at 11:30 +0800, wenzong.fan@windriver.com wrote:
>
> > Make an explicit dependency to the libs install targets would fix this
> > issue.
>
> I don't think Yocto should be running the 'make install' target with
> parallelism enabled; it's just going to be a source of major pain for
> small gain. Historically Automake's install targets have had a lot of
> paralleism issues AIUI, even discarding modules which have custom
> install hooks.
We did used to steer clear of this but more recently tested it out and
with a few exceptions (which we disabled with PARALLEL_MAKEINST=""),
parallel make install seems to work fine and did give a small but
measurable speed-up (I'd have to look at the archives to remember what).
It helps that we use the latest automake everywhere and regenerate all
the makefiles ourselves.
So whilst I agree with this from a historical perspective, times so seem
to be changing and improving. If there are issues I do want to know
about and deal with them though.
Cheers,
Richard
next prev parent reply other threads:[~2012-08-06 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 3:30 [PATCH 0/1] gdk-pixbuf: fix parallel install issue wenzong.fan
2012-08-03 3:30 ` [PATCH 1/1] " wenzong.fan
2012-08-05 22:32 ` Colin Walters
2012-08-06 6:56 ` wenzong fan
2012-08-06 12:55 ` Richard Purdie [this message]
2012-08-06 13:24 ` Koen Kooi
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=1344257725.9756.147.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox