On Mon, Feb 13, 2012 at 7:40 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
<snip>
> meta/recipes-gnome/gtk+/gtk+_2.24.8.bb | 2 +-
The rebuild of gtk+ triggered by this commit fails on my quad core
build machine:
| configure: error: Package requirements (cairo-xlib >= 1.6) were not met:
|
| No package 'cairo-xlib' found
I won't have time to look into this until this evening or tomorrow
morning, but will send a patch when I find a fix.
Unless someone beats me to it :-)
Steve

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"
>> I won't have time to look into this until this evening or tomorrow> morning, but will send a patch when I find a fix.>> Unless someone beats me to it :-)

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.
On my other build machine (the 8 core) some other package must be
triggering cairo to build with xlib enabled and I don't get the gtk+
error.
Not sure what the proper fix is. Suggestions welcome. In order to
get work done I'll probably append x11 to distro features in my layer
and deal with it when I have more time.
Steve

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.

On Tue, Feb 21, 2012 at 1:33 PM, Phil Blundell <philb@gnu.org> wrote:
> 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.
Agreed! But it does :-(
> 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?
Well, this is an image for a headless system, so neither directfb nor
x11 will be used! I'm not really sure what package is causing gtk+ to
be built.
Steve

On Tuesday 21 February 2012 13:16:11 Steve Sakoman wrote:
> Since Poky doesn't have x11 in DISTRO_FEATURES, cairo builds without> xlib support by default.
If you're referring to the default configuration, I can assure you Poky does
have x11 in DISTRO_FEATURES.
Cheers,
Paul

On Tue, 2012-02-21 at 13:39 -0800, Steve Sakoman wrote:
> Well, this is an image for a headless system, so neither directfb nor> x11 will be used! I'm not really sure what package is causing gtk+ to> be built.
Ah. Well, gtk+ 2.x requires you to choose exactly one of either x11 or
directfb as the backend. If you don't have either then it isn't going
to work.
You can use "bitbake -g" to find out what is depending on gtk+, or just
add gtk+ to BBMASK and see which recipe starts complaining about
unsatisfied dependencies. Sounds like eliminating that dependency at
source is probably going to be the most fruitful route for you to
explore.
p.

On Tue, Feb 21, 2012 at 1:44 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Tuesday 21 February 2012 13:16:11 Steve Sakoman wrote:>> Since Poky doesn't have x11 in DISTRO_FEATURES, cairo builds without>> xlib support by default.>> If you're referring to the default configuration, I can assure you Poky does> have x11 in DISTRO_FEATURES.
The ELC flu is affecting my ability to think :-(
I see now that Poky relies on the DISTRO_FEATURES setup in
bitbake.conf (via default-distrovars.inc via defaultsetup.conf). I
was just looking in poky.conf and didn't see anywhere that it pulled
in either of those files.
So now I need to figure out why the quad core machine is refusing to
enable --with-x=yes for the cairo build . . .
Perhaps better to wait till tomorrow when I am feeling better.
Steve