From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xineramaproto
Date: Fri, 11 Oct 2013 14:48:36 +0200 [thread overview]
Message-ID: <20131011144836.6a22ca05@skate> (raw)
In-Reply-To: <233A67DA67A045DF84F76ABF9CA04635@tux.local>
Dear Gwyll Gwyllin,
On Thu, 10 Oct 2013 14:16:14 +0200, Gwyll Gwyllin wrote:
> i?m trying to cross compile (for MIPS) but i?m stucked at xserver_xorg-xserver-1.5.2
Hum, which version of Buildroot are you using? 1.5.2 was the X.org
server packaged in Buildroot before July 2009 or something like that.
Maybe you should upgrade to benefit from all the testing and
improvements we've done since then. In 2009, we didn't had the
autobuilders that we have today, and since we have that, the amount of
testing Buildroot receives has increased significantly.
> The compiler error says:
>
> checking for a useful monotonic clock ...... cross compiling
> checking for strcasecmp... yes
> checking for strncasecmp... yes
> checking for strcasestr... (cached) yes
> checking for XDMCP... yes
> checking for XdmcpWrap in -lXdmcp... yes
> checking for XSERVERCFLAGS... configure: error: Package requirements (randrproto >= 1.2 renderproto fixesproto >= 4.0 damageproto >= 1.1 xcmiscproto xextproto xproto >= 7.0.9 xtrans scrnsaverproto >= 1.1 bigreqsproto resourceproto fontsproto inputproto >= 1.4.4 kbproto >= 1.0.3 videoproto compositeproto >= 0.4 resourceproto xineramaproto evieproto xkbfile xfont xau fontenc pixman-1 >= 0.9.5 dbus-1 xdmcp) were not met:
>
> No package 'xineramaproto' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables XSERVERCFLAGS_CFLAGS
> and XSERVERCFLAGS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> pkg-config ?modversion xineramaproto says 1.1.2
Yes, if you're using the pkg-config from your host machine, it will
tell you that xineramaproto is installed on your host machine. But that
doesn't tell anything about whether it's available for your target.
It seems like there is a missing dependency in the X server
Buildroot .mk file on the xinerama proto package, or a missing
--disable-xinerama in the X server configuration options.
> I tried to set PKG_CONFIG_PATH to /usr/lib/pkg-config, the result was the same.
That's plain wrong. /usr/lib/pkg-config contains the description of
libraries built for your host. Using them for your target is just going
to make the build fail even more.
I would definitely recommend upgrading your Buildroot version. An
open-source community unfortunately cannot afford supporting users that
use such old version: we've fixed gazillions of problems since 2009.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-11 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 12:16 [Buildroot] Xineramaproto Gwyll Gwyllin
2013-10-11 12:48 ` Thomas Petazzoni [this message]
[not found] ` <BAF922FAE74849899122A8651F8AFD3C@tux.local>
2013-11-12 10:15 ` Gwyll Gwyllin
2013-11-12 10:58 ` Thomas Petazzoni
2013-11-15 14:00 ` Gwyll Gwyllin
2013-11-15 14:15 ` 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=20131011144836.6a22ca05@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