From: Gary Thomas <gary@mlbassoc.com>
To: Tom Rini <tom_rini@mentor.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: FireFox on PowerPC
Date: Sat, 03 Apr 2010 19:44:02 -0600 [thread overview]
Message-ID: <4BB7EEE2.9060408@mlbassoc.com> (raw)
In-Reply-To: <1270336288.3653.45.camel@trini-m4400>
On 04/03/2010 05:11 PM, Tom Rini wrote:
> On Sat, 2010-04-03 at 11:22 -0600, Gary Thomas wrote:
>> On 04/03/2010 10:40 AM, Tom Rini wrote:
>>> On Sat, 2010-04-03 at 09:28 -0600, Gary Thomas wrote:
>>>
>>>> That said, this seems to be a [Make] parallelism problem, not clear why/how.
>>>> If I just rerun 'bitbake firefox' which restarts the compile step, it will
>>>> run to completion. I do normally use -j4, but disabling this did not seem
>>>> to make any difference.
>>>>
>>>> Note: the previous version I built (3.5.2) did not exhibit this behaviour.
>>>
>>> Well that's depressing since we just added the best we can tell correct
>>> magic to build firefox with make -jN. If you put PARALLEL_MAKE = "" in
>>> the .bb, does it complete this time?
>>>
>>
>> No change, I'm afraid.
>
> Interesting. From log.do_compile, was make -jN taken out? I kinda fear
> not...
>
I see only -j1 in the logs
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-04-04 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 13:59 FireFox on PowerPC Gary Thomas
2010-03-31 14:58 ` Martyn Welch
2010-03-31 14:59 ` Gary Thomas
2010-03-31 17:06 ` Khem Raj
2010-03-31 17:13 ` Gary Thomas
2010-03-31 17:36 ` Tom Rini
2010-04-03 15:28 ` Gary Thomas
2010-04-03 16:40 ` Tom Rini
2010-04-03 17:22 ` Gary Thomas
2010-04-03 23:11 ` Tom Rini
2010-04-04 1:44 ` Gary Thomas [this message]
2010-04-06 13:04 ` Gary Thomas
2010-04-07 2:52 ` Tom Rini
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=4BB7EEE2.9060408@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=tom_rini@mentor.com \
/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