[meta-browser] Question regarding status of chromium recipes

[meta-browser] Question regarding status of chromium recipes

[Chris Larson]

Greetings,

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 :)
-- 
Christopher Larson
clarson at kergoth dot com
Senior Software Engineer, Mentor Graphics

Re: [meta-browser] Question regarding status of chromium recipes

[Mario Domenech Goulart]

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?

Best wishes.
Mario

Re: [meta-browser] Question regarding status of chromium recipes

[Gary Thomas]

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
------------------------------------------------------------

Re: [meta-browser] Question regarding status of chromium recipes

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 25-10-12 20:01, Chris Larson schreef:
> Greetings,
> 
> 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 :)

Nice timing, I just received a request for a working chromium build and I
ran into similar if not the same issues :)



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQibx8MkyGM64RGpERAuWWAJ9ooRxIMeMmyWCAT5gCkfYjrx05NwCgso/G
hWVMQT8AZkx2MOXqsr+xARc=
=2i+V
-----END PGP SIGNATURE-----

Re: [meta-browser] Question regarding status of chromium recipes

[Denis 'GNUtoo' Carikli]

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.
I rebuilt from scratch locally the SHR packages and images some days
ago, that included chromium....
And it produced 3 ipk:
chromium_19.0.1049.3-r1_armv7a-vfp-neon.ipk
chromium-dbg_19.0.1049.3-r1_armv7a-vfp-neon.ipk
chromium-dev_19.0.1049.3-r1_armv7a-vfp-neon.ipk

I then installed them with opkg install that fetch it from my local
feed.

I tested a bit youtube in html5 and it worked fine...(I had to create a
non-root account to make chromium start tough).

Patches for fixing the issues you have are welcome.

Denis.