From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] recipes: bump PR to rebuild .la files without libz.la
Date: Tue, 21 Feb 2012 21:33:41 +0000 [thread overview]
Message-ID: <1329860021.2591.182.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAGDS+nn7+3zVFX896P-+y5tT4Xw-++bgKtizmDsFZUno5D9Y8A@mail.gmail.com>
On Tue, 2012-02-21 at 13:16 -0800, Steve Sakoman wrote:
> On Tue, Feb 21, 2012 at 1:07 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Tue, Feb 21, 2012 at 11:25 AM, Steve Sakoman <sakoman@gmail.com> wrote:
> >>
> >> | configure: error: Package requirements (cairo-xlib >= 1.6) were not met:
> >> |
> >> | No package 'cairo-xlib' found
> >
> > Add DEPENDS += "cairo"
>
> Nope, cairo is already in the DEPENDS list for gtk+.
>
> Seems the issue is that on that build machine (the 4 core) cairo isn't
> being built with --with-x=yes.
>
> The cairo recipe checks for x11 in DISTRO_FEATURES and does
> --with-x=yes if it is present.
>
> Since Poky doesn't have x11 in DISTRO_FEATURES, cairo builds without
> xlib support by default.
If you don't have x11 in DISTRO_FEATURES then I wouldn't have expected
gtk+ to want cairo-x11 either. Though, I don't quite know what the gtk+
configury will do if you don't select any backends at all and it's
possible it might be falling back to X in that case.
What gtk backend are you expecting to use - directfb?
p.
next prev parent reply other threads:[~2012-02-21 21:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 15:40 [PATCH 0/4] PR bumps for missing libz.la, resent gdb python support with fix Martin Jansa
2012-02-13 15:40 ` [PATCH 1/4] gdb-cross-canadian: build gdb with python support Martin Jansa
2012-02-13 15:40 ` [PATCH 2/4] gdb-cross-canadian: use NATIVESDK paths as it happens to be here Martin Jansa
2012-02-13 16:11 ` [PATCH] gdb-cross-canadian: bump PR Martin Jansa
2012-02-17 22:36 ` [PATCH 2/4] gdb-cross-canadian: use NATIVESDK paths as it happens to be here Saul Wold
2012-02-18 11:56 ` Martin Jansa
2012-02-18 14:01 ` Richard Purdie
2012-02-23 8:16 ` Martin Jansa
2012-02-23 10:27 ` Richard Purdie
2012-02-25 0:05 ` Martin Jansa
2012-02-25 1:02 ` Richard Purdie
2012-02-25 13:12 ` Martin Jansa
2012-02-25 15:42 ` Richard Purdie
2012-02-13 15:40 ` [PATCH 3/4] zlib: remove ldconfig call from install-libs Martin Jansa
2012-02-13 15:40 ` [PATCH 4/4] recipes: bump PR to rebuild .la files without libz.la Martin Jansa
2012-02-21 19:00 ` Steve Sakoman
2012-02-21 19:25 ` Steve Sakoman
2012-02-21 21:07 ` Khem Raj
2012-02-21 21:16 ` Steve Sakoman
2012-02-21 21:33 ` Phil Blundell [this message]
2012-02-21 21:39 ` Steve Sakoman
2012-02-21 21:45 ` Phil Blundell
2012-02-21 21:44 ` Paul Eggleton
2012-02-21 22:01 ` Steve Sakoman
2012-02-21 17:07 ` [PATCH 0/4] PR bumps for missing libz.la, resent gdb python support with fix Saul Wold
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=1329860021.2591.182.camel@x121e.pbcl.net \
--to=philb@gnu.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 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.