From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Wolfgang Denk <wd@denx.de>
Cc: poky@yoctoproject.org, Joshua Lock <josh@linux.intel.com>
Subject: Re: [PATCH 0/3] Misc build fixes v2
Date: Tue, 21 Dec 2010 14:45:59 +0000 [thread overview]
Message-ID: <1292942759.25087.6137.camel@rex> (raw)
In-Reply-To: <20101221072706.A79A3B715C@gemini.denx.de>
On Tue, 2010-12-21 at 08:27 +0100, Wolfgang Denk wrote:
> Dear Joshua Lock,
>
> In message <cover.1292856365.git.josh@linux.intel.com> you wrote:
> > This series includes a corrected fix for gst-plugins-base for make 3.82 as
> > well as a more correct fix to enable gthumb to build on a system without
> > gtk-doc installed.
> >
> > We do this by providing a gtk-doc-native recipe and having gtk-doc depend on
> > it. That way we have a binary to run on the build system to generate the
> > documentation as well as a target version so that the pkgconfig test passes.
> >
> > Pull URL: git://git.pokylinux.org/poky-contrib.git
> > Branch: josh/make-382
> > Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=josh/make-382
>
> I confirm that I can build both poky-image-sdk and meta-toolchain-sdk
> for "qemuppc" on Fedora 14 / x86_64 with these patches.
>
> Tested-by: Wolfgang Denk <wd@denx.de>
Great, I'm pleased this is working better now. Thanks for reporting
back!
(and thanks Joshua for sorting the issues!)
Cheers,
Richard
prev parent reply other threads:[~2010-12-21 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 14:46 [PATCH 0/3] Misc build fixes v2 Joshua Lock
2010-12-14 17:56 ` [PATCH 1/3] gst-plugins: fix for make 3.82 Joshua Lock
2010-12-17 14:09 ` [PATCH 2/3] gnome-common: add native variant via BBCLASSEXTEND Joshua Lock
2010-12-17 14:09 ` [PATCH 3/3] gnome-doc-utils: ensure a native variant exists for document generation Joshua Lock
2010-12-21 7:27 ` [PATCH 0/3] Misc build fixes v2 Wolfgang Denk
2010-12-21 14:45 ` Richard Purdie [this message]
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=1292942759.25087.6137.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=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