From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser] Question regarding status of chromium recipes
Date: Fri, 26 Oct 2012 00:26:04 +0200 [thread overview]
Message-ID: <k6ce9q$6ec$1@ger.gmane.org> (raw)
In-Reply-To: <CABcZANmC_c-fZMBHH4tc7gvJdrs_UPoFhn19X+T1E7beqRbXLQ@mail.gmail.com>
-----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-----
next prev parent reply other threads:[~2012-10-25 22:39 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
2012-10-25 22:26 ` Koen Kooi [this message]
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='k6ce9q$6ec$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.