Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: FireFox on PowerPC
Date: Sat, 03 Apr 2010 09:28:09 -0600	[thread overview]
Message-ID: <4BB75E89.6030708@mlbassoc.com> (raw)
In-Reply-To: <1270056997.6277.89.camel@trini-m4400>

On 03/31/2010 11:36 AM, Tom Rini wrote:
> On Wed, 2010-03-31 at 11:13 -0600, Gary Thomas wrote:
>> On 03/31/2010 11:06 AM, Khem Raj wrote:
>>> On Wed, Mar 31, 2010 at 6:59 AM, Gary Thomas<gary@mlbassoc.com>   wrote:
>>>> Has anyone had success building FireFox for a PowerPC
>>>> target - I'm using the development branch (org.openembedded.dev)
>>>>    MACHINE=efika
>>>>    DISTRO = "angstrom-2008.1"
>>>>
>>>> I've tried to build a number of different FireFox packages,
>>>> none with success.  So far I've tried 2.0.0.3, 3.5.2&   3.6.2
>>>>
>>>> Any pointers?
>>>>
>>>> Query: is there an easy way to build a particular package version?
>>>> What I've done is just add a line like this to my local.conf:
>>>>    PREFERRED_VERSION_firefox="3.5.2"
>>>
>>>
>>> what errors do you get.
>>
>> It depends on the version.  For 3.6.2 (latest), I get this:
>>
>> ccache powerpc-angstrom-linux-g++ -mcpu=603e -mhard-float  -L/local/Angstrom_BeagleBoard/tmp/staging/ppc603e-angstrom-linux/usr/lib
>> -Wl,-rpath-link,/local/Angstrom_BeagleBoard/tmp/staging/ppc603e-angstrom-linux/usr/lib -Wl,-O1 -Wl,--hash-style=gnu -o jsbool.o -c -fvisibility=hidden -DOSTYPE=\"Linux\"
>> -DOSARCH=Linux -DEXPORT_JS_API  -DJS_USE_SAFE_ARENA  -I. -I. -I./../../dist/include -I./../../dist/include/nsprpub
>> -I/local/Angstrom_BeagleBoard/tmp/work/ppc603e-angstrom-linux/firefox-3.6.2-r0/mozilla-1.9.2/dist/include/nspr   -I.    -fPIC
>> -isystem/local/Angstrom_BeagleBoard/tmp/staging/ppc603e-angstrom-linux/usr/include  -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth
>> -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Wno-long-long -pedantic
>> -isystem/local/Angstrom_BeagleBoard/tmp/staging/ppc603e-angstrom-linux/usr/include -Os -fsigned-char -fno-strict-aliasing -fpermissive -fvisibility-inlines-hidden
>> -fno-strict-aliasing -pthread -pipe  -DNDEBUG -DTRIMMED -g -fno-inline -O2  -isystem/local/Angstrom_BeagleBoard/tmp/staging/ppc603e-angstrom-linux/usr/include  -DMOZILLA_CLIENT
>> -include ./js-confdefs.h -Wp,-MD,.deps/jsbool.pp jsbool.cpp
>> jsapi.cpp: In function 'JSBool JS_ConvertArgumentsVA(JSContext*, uintN, jsval*, const char*, __va_list_tag*)':
>> jsapi.cpp:289: error: cannot convert '__va_list_tag**' to '__va_list_tag (*)[1]' for argument '5' to 'JSBool TryArgumentFormatter(JSContext*, const char**, JSBool, jsval**,
>> __va_list_tag (*)[1])'
>> jsapi.cpp: In function 'jsval* JS_PushArgumentsVA(JSContext*, void**, const char*, __va_list_tag*)':
>> jsapi.cpp:398: error: cannot convert '__va_list_tag**' to '__va_list_tag (*)[1]' for argument '5' to 'JSBool TryArgumentFormatter(JSContext*, const char**, JSBool, jsval**,
>> __va_list_tag (*)[1])'
>> make[4]: *** [jsapi.o] Error 1
>> make[4]: *** Waiting for unfinished jobs....
>> make[4]: Leaving directory `/local/Angstrom_BeagleBoard/tmp/work/ppc603e-angstrom-linux/firefox-3.6.2-r0/mozilla-1.9.2/js/src'
>> make[3]: *** [libs_tier_js] Error 2
>> make[3]: Leaving directory `/local/Angstrom_BeagleBoard/tmp/work/ppc603e-angstrom-linux/firefox-3.6.2-r0/mozilla-1.9.2'
>> make[2]: *** [tier_js] Error 2
>> make[2]: Leaving directory `/local/Angstrom_BeagleBoard/tmp/work/ppc603e-angstrom-linux/firefox-3.6.2-r0/mozilla-1.9.2'
>> make[1]: *** [default] Error 2
>> make[1]: Leaving directory `/local/Angstrom_BeagleBoard/tmp/work/ppc603e-angstrom-linux/firefox-3.6.2-r0/mozilla-1.9.2'
>> make: *** [build] Error 2
>> FATAL: oe_runmake failed
>>
>> Note: to even get this far, I had to apply the attached patch
>> as the default setup falls apart with regard to va_list processing.
>
> Oh man that takes me (and I bet you too) back... Sounds like mozilla
> needs some patching again.  Maybe the ppcnux folks have one somewhere
> already tho?
>

I didn't find anything there.

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.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



  reply	other threads:[~2010-04-03 15:31 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 [this message]
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
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=4BB75E89.6030708@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-devel@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