From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5462] webkit doesn't build on directfb
Date: Sat, 18 Aug 2012 07:01:50 -0500 [thread overview]
Message-ID: <201208180701.53228.minimod@morethan.org> (raw)
In-Reply-To: <20120817161626.D0E9C971EA@busybox.osuosl.org>
On Fri August 17 2012, bugzilla at busybox.net wrote:
> https://bugs.busybox.net/show_bug.cgi?id=5462
>
> --- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 2012-08-17 16:16:26 UTC ---
> Thanks Vincent for the report. It is similar to
> http://autobuild.buildroot.net/results/74637e3a3e4c37c3af0f3662504c28332e9c586c/build-end.log.
>
> We need to investigate if this is really Webkit that doesn't support DirectFB
> as a Gtk backend. If this is the case, then we simply need to prevent Webkit
> from being built if the selected Gtk backend is DirectFB.
>
> Or it is just a bug in Webkit that shouldn't include this header file, or
> should include it conditionnally or something like that.
>
> I personaly don't have enough time right now to dig into Webkit, so if you
> could have a look at this and give us your conclusions, it would be great.
> Thanks!
>
The Kindle K4 and K5 come from the factory with a webkit browser that
works on the directFB device.
Not sure if it is using Gtk, but it is using X11.
Mike
next prev parent reply other threads:[~2012-08-18 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 12:40 [Buildroot] [Bug 5462] New: webkit doesn't build on directfb bugzilla at busybox.net
2012-08-17 12:41 ` [Buildroot] [Bug 5462] " bugzilla at busybox.net
2012-08-17 16:16 ` bugzilla at busybox.net
2012-08-18 12:01 ` Michael S. Zick [this message]
2012-08-21 11:54 ` Thomas Petazzoni
2013-05-26 17:06 ` bugzilla at busybox.net
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=201208180701.53228.minimod@morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.net \
/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