From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] webkit-gtk: Use glib as unicode backend to avoid browser crash
Date: Fri, 01 Jun 2012 09:22:37 +0100 [thread overview]
Message-ID: <1338538957.20169.264.camel@ted> (raw)
In-Reply-To: <4FC66D5B.7090201@mlbassoc.com>
On Wed, 2012-05-30 at 12:56 -0600, Gary Thomas wrote:
> On 2012-05-30 10:40, Richard Purdie wrote:
> > On Wed, 2012-05-30 at 17:08 +0800, edwin.zhai@intel.com wrote:
> >> From: Zhai Edwin<edwin.zhai@intel.com>
> >>
> >> webkit-gtk depends on ICU for the unicode, but ICU is not safe when build and
> >> target system owns different endian. ICU's community is not responsive to make
> >> a patch for this, so glib is used as work around here.
> >>
> >> [YOCTO #1570] got fixed
> >>
> >> Signed-off-by: Zhai Edwin<edwin.zhai@intel.com>
> >> ---
> >> meta/recipes-sato/webkit/webkit-gtk_svn.bb | 10 +++++++++-
> >> 1 files changed, 9 insertions(+), 1 deletions(-)
> >
> > I've merged this however I'm not 100% happy with this as the final fix.
> > I'd ask that:
> >
> > a) The bug remains open (re-prioritised appropriately) about the
> > remaining issues that still exist in ICU
> > b) We add something to the ICU recipe which stops it building when the
> > endianess isn't correct (host matches target) so nobody can built it and
> > have it not work.
>
> Why not accept my patch that provides a working dataset? I doubt
> that you're ever going to get the ICU folks interested to the point
> of fixing this correctly and this solves the problem without the
> [IMO undesirable] side effect of using different libraries on
> different architectures (for webkit-gtk).
The issue here is that starting to distribute binary blobs gets us into
potentially troubled waters. It also means that for every new tune or
target (say mips BE), we'd need another blob. Add something like uclibc
and the problem gets worse.
So I can see the attraction of the solution and it works well for
particular cases but it isn't something I think can be made to work in
OE-Core in the general case :(.
I did wonder whether we could post process the binary to correct the
endianess of the data in the file?
Cheers,
Richard
next prev parent reply other threads:[~2012-06-01 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 9:08 [PATCH 0/1] Fix browser crash on PPC edwin.zhai
2012-05-30 9:08 ` [PATCH 1/1] webkit-gtk: Use glib as unicode backend to avoid browser crash edwin.zhai
2012-05-30 16:40 ` Richard Purdie
2012-05-30 18:56 ` Gary Thomas
2012-06-01 0:56 ` Zhai, Edwin
2012-06-01 8:22 ` Richard Purdie [this message]
2012-06-01 1:33 ` RPM packaging issue? Laurentiu Palcu
2012-06-01 15:10 ` Mark Hatle
2012-05-30 11:05 ` [PATCH 0/1] Fix browser crash on PPC Gary Thomas
2012-05-30 12:05 ` Koen Kooi
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=1338538957.20169.264.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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