From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser] Question regarding status of chromium recipes
Date: Thu, 25 Oct 2012 13:09:30 -0600 [thread overview]
Message-ID: <50898E6A.60403@mlbassoc.com> (raw)
In-Reply-To: <85ip9ywhjw.fsf@cl-t066-141cl.privatedns.com>
On 2012-10-25 12:08, Mario Domenech Goulart wrote:
> Hi Chris,
>
> On Thu, 25 Oct 2012 11:01:00 -0700 Chris Larson <clarson@kergoth.com> wrote:
>
>> I'm wondering if the chromium recipes in this layer have ever been
>> build tested. As far as I can tell, both 19 and 20 are missing
>> dependencies on udev (libudev), gtk+, and gconf, and 20 also wants the
>> openssl headers. 19 also fails due to an attempt to build/link a
>> native tool requiring libxi, so it seems it can't be built without x11
>> headers on the build machine (along with the odd ld.gold requirement).
>> Given these issues, I figured I'd throw out a contact email and try
>> to determine if perhaps the OSSystems folks have local changes that
>> never made it into the public layer, or if the recipes just didn't get
>> a great deal of testing.
>>
>> Thanks, I'd appreciate any input on their status :)
>
> I haven't built chromium on OE. I've been building firefox only. Maybe
> Otavio?
I just gave it a try and it failed pretty early on with an error in one of
the support packages:
| arm-amltd-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/home/local/p60_new/tmp/sysroots/cobra3530p60 -o
Linux2.6_arm_glibc_PTH_OPT.OBJ/secport.o -c -O2 -pipe -g -feliminate-unused-debug-types -ansi -D_POSIX_SOURCE -D_BSD_SOURCE -D_XOPEN_SOURCE -fPIC -DLINUX2_1 -Wall
-Werror-implicit-function-declaration -Wno-switch -pipe -DLINUX -Dlinux -DHAVE_STRERROR -DXP_UNIX -UDEBUG -DNDEBUG -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY
-I/home/local/p60_new/tmp/sysroots/cobra3530p60/usr/include/mozilla/nspr -I../../../../dist/Linux2.6_arm_glibc_PTH_OPT.OBJ/include -I../../../../dist/public/nss
-I../../../../dist/private/nss secport.c
| secport.c: In function 'PORT_FreeArena_Util':
| secport.c:347:2: error: implicit declaration of function 'PL_ClearArenaPool' [-Werror=implicit-function-declaration]
| cc1: some warnings being treated as errors
| make[2]: *** [Linux2.6_arm_glibc_PTH_OPT.OBJ/secport.o] Error 1
| make[2]: Leaving directory `/home/local/p60_new/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/nss-3.13.3-r1/nss-3.13.3/mozilla/security/nss/lib/util'
| make[1]: *** [libs] Error 2
| make[1]: Leaving directory `/home/local/p60_new/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/nss-3.13.3-r1/nss-3.13.3/mozilla/security/nss/lib'
| make: *** [libs] Error 2
| make: Leaving directory `/home/local/p60_new/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/nss-3.13.3-r1/nss-3.13.3/mozilla/security/nss'
| ERROR: Function failed: do_compile (see /home/local/p60_new/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/nss-3.13.3-r1/temp/log.do_compile.2781 for further information)
ERROR: Task 173 (/home/local/poky-multi/meta-browser/recipes-support/nss/nss_3.13.3.bb, do_compile) failed with exit code '1'
Maybe there's a known cure for this?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-10-25 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 18:01 [meta-browser] Question regarding status of chromium recipes Chris Larson
2012-10-25 18:08 ` Mario Domenech Goulart
2012-10-25 19:09 ` Gary Thomas [this message]
2012-10-25 22:26 ` Koen Kooi
2012-10-30 11:04 ` Denis 'GNUtoo' Carikli
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=50898E6A.60403@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