Poky Project Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/4] Misc build fixes
Date: Mon, 20 Dec 2010 12:23:13 +0000	[thread overview]
Message-ID: <1292847793.2466.18.camel@scimitar> (raw)
In-Reply-To: <20101220092911.AF1F8CDE29A@gemini.denx.de>

On Mon, 2010-12-20 at 10:29 +0100, Wolfgang Denk wrote:
> Dear Joshua,
> 
> In message <cover.1292600657.git.josh@linux.intel.com> you wrote:
> > This series includes a corrected fix for gst-plugins-base for make 3.82 as
> > well as fixes to enable gthumb to build on a system without gtk-doc installed
> 
> Thanks.
> 
> >   gthumb: add gnome-doc-utils-native to DEPENDS
> 
> Using your poky-contrib/josh/make-382git branch and trying to build
> poky-image-sdk for qemuppc on F14 results for me in this:
> 
> ...
> | checking dynamic linker characteristics... (cached) GNU/Linux ld.so
> | checking how to hardcode library paths into programs... immediate
> | checking for glib-genmarshal... /opt/poky/build-work-qemuppc/tmp/sysroots/x86_64-linux/usr/bin/glib-genmarshal
> | checking for glib-mkenums... /opt/poky/build-work-qemuppc/tmp/sysroots/x86_64-linux/usr/bin/glib-mkenums
> | checking for powerpc-poky-linux-pkg-config... no
> | checking for pkg-config... /opt/poky/build-work-qemuppc/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
> | configure: WARNING: using cross tools not prefixed with host triplet
> | checking pkg-config is at least version 0.9.0... yes
> | checking gnome-doc-utils >= 0.3.2... no
> | configure: error: gnome-doc-utils >= 0.3.2 not found
> | FATAL: oe_runconf failed
> | ERROR: Task failed: ('function do_configure failed', '/opt/poky/build-work-qemuppc/tmp/work/ppc603e-poky-linux/gthumb-2.12.0-r2/temp/log.do_configure.5399')
> NOTE: package gthumb-2.12.0-r2: task do_configure: Failed
> ERROR: Task 1387 (/home/wd/git/poky/work/meta/recipes-gnome/gthumb/gthumb_2.12.0.bb, do_configure) failed with 1
> ERROR: '/home/wd/git/poky/work/meta/recipes-gnome/gthumb/gthumb_2.12.0.bb' failed
> 
> Am I missing something?

Ah, of course - we need the non-native variant of gnome-doc-utils to
pass the pkg-config check...

As you've discovered (on IRC) you can work around this by manually
building gnome-doc-utils - I will work out a patch for this today.

Thanks for reporting,

Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre



  reply	other threads:[~2010-12-20 12:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 15:44 [PATCH 0/4] Misc build fixes Joshua Lock
2010-12-14 17:56 ` [PATCH 1/4] gst-plugins: fix for make 3.82 Joshua Lock
2010-12-17 14:09 ` [PATCH 2/4] gnome-common: add native variant via BBCLASSEXTEND Joshua Lock
2010-12-17 14:09 ` [PATCH 3/4] gnome-doc-utils: add native variant using BBCLASSEXTEND Joshua Lock
2010-12-17 14:11 ` [PATCH 4/4] gthumb: add gnome-doc-utils-native to DEPENDS Joshua Lock
2010-12-20  9:29 ` [PATCH 0/4] Misc build fixes Wolfgang Denk
2010-12-20 12:23   ` Joshua Lock [this message]
2010-12-20 12:47 ` Joshua Lock

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=1292847793.2466.18.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=poky@yoctoproject.org \
    --cc=wd@denx.de \
    /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