From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Webkit compilation broken without X11
Date: Tue, 9 Oct 2012 11:17:01 +0200 [thread overview]
Message-ID: <20121009111701.42bb68af@skate> (raw)
In-Reply-To: <5073DF9C.5030505@relinux.de>
Dear Stephan Hoffmann,
On Tue, 09 Oct 2012 10:26:04 +0200, Stephan Hoffmann wrote:
> I am currently trying to compile webkit for my beaglebone using
> directfb (without X11). Unfortunatelly, compilation stops because of
> missing X11 headers. This also happens with the qemu_arm_versatile
> defconfig.
>
> > In file included from ./WebCore/bridge/npruntime_internal.h:28:0,
> > from ./WebCore/plugins/PluginStream.h:40,
> > from ./WebCore/plugins/PluginView.h:36,
> > from
> > WebCore/bindings/js/ScriptControllerGtk.cpp:35: ./WebCore/bridge/npapi.h:105:26:
> > fatal error: X11/Xlib.h: No such file or directory
> > compilation terminated.
> > make[2]: ***
> > [WebCore/bindings/js/libwebkit_1_0_la-ScriptControllerGtk.lo]
> > Fehler 1
>
> In 2012.05 Webkit compiles o.k.
>
> Attached you find the modified defconfig to reproduce this failure.
Yes, the problem is well-known, and someone who cares about Webkit on
DirectFB needs to dig into it. Can you investigate? Maybe it's just a
header inclusion lacking the proper #ifdef, or maybe it's more
problematic (DirectFB support in Webkit not being well-maintained, for
example).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-09 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 8:26 [Buildroot] Webkit compilation broken without X11 Stephan Hoffmann
2012-10-09 9:17 ` Thomas Petazzoni [this message]
2012-10-09 10:42 ` Stephan Hoffmann
2012-10-09 10:53 ` Thomas Petazzoni
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=20121009111701.42bb68af@skate \
--to=thomas.petazzoni@free-electrons.com \
--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