From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gtk-doc: Ensure we run gtkdocize else we could see build failures (e.g. evolution-data-server)
Date: Sun, 22 Jul 2012 13:13:20 +0100 [thread overview]
Message-ID: <1342959200.21788.74.camel@ted> (raw)
In-Reply-To: <35FBB7A8207843A5AFC9AF27326C7ABC@intel.com>
On Fri, 2012-07-20 at 20:29 +0100, Ross Burton wrote:
> On Friday, 20 July 2012 at 16:55, Richard Purdie wrote:
> > This is a fix to Ross' series, we need to run gtkdocize in case anything
> > was built from source control and the appropriate files are missing.
>
> Good point but I'm curious how the build was succeeding/what broke before this.
Probably you used an existing build which already had the gtk-doc.make
file touched and your didn't bump PR. The file therefore hung around. It
would only happen on something built from SCM (evolution-data-server is
a git recipe).
I'm guessing if you clean eds, it would show up.
Cheers,
Richard
prev parent reply other threads:[~2012-07-22 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 15:55 [PATCH] gtk-doc: Ensure we run gtkdocize else we could see build failures (e.g. evolution-data-server) Richard Purdie
2012-07-20 19:29 ` Ross Burton
2012-07-22 12:13 ` 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=1342959200.21788.74.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.