From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Pending "big" patch series
Date: Fri, 26 Sep 2014 18:47:17 +0200 [thread overview]
Message-ID: <20140926184717.0c2d6822@free-electrons.com> (raw)
In-Reply-To: <20140923213752.GA5923@itchy>
Hello Eric,
On Tue, 23 Sep 2014 23:37:52 +0200, Eric Le Bihan wrote:
> I had a quick look at the webkit patch. Webkit is a strange beast with issues
> when building with parallelism activated. When building version 2.4.3, I
> encountered the bug mentioned in the commit log, and when I bumped to 2.4.5,
> I've found more parallel build issues (and some ARM ASM ones too).
Argh. Not being able to build Webkit in parallel would be quite
annoying: it's a really huge package, so building in parallel brings a
significant build time reduction.
Regarding the bug in 2.4.3, it seems to be potentially a bug in make
itself, because make takes 100% of CPU time and is completely stuck. I
have compiled a host make with debugging symbols, but I haven't had the
time to reproduce the build.
> It looks like version 2.6.0 is on its way. The build system now uses cmake
> instead of autotools. I'll try a bump to 2.5.90 to see if the issues are
> solved.
Great!
> BTW, why is this package still called "webkit" whereas it is in fact
> "webkit-gtk"?
Purely historical reasons I believe.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-26 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 10:53 [Buildroot] Pending "big" patch series Thomas Petazzoni
2014-09-14 11:10 ` Yann E. MORIN
2014-09-14 18:41 ` Thomas De Schampheleire
2014-09-14 19:46 ` Yann E. MORIN
2014-09-23 18:02 ` Thomas Petazzoni
2014-09-23 19:41 ` Thomas De Schampheleire
2014-09-23 21:37 ` Eric Le Bihan
2014-09-26 16:47 ` Thomas Petazzoni [this message]
2014-12-27 21:49 ` Thomas Petazzoni
2014-10-02 19:29 ` Thomas De Schampheleire
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=20140926184717.0c2d6822@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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