From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Problem with gettext-native
Date: Thu, 02 Jun 2011 18:21:43 +0100 [thread overview]
Message-ID: <1307035303.27470.584.camel@rex> (raw)
In-Reply-To: <4DE79F0A.5080104@mlbassoc.com>
On Thu, 2011-06-02 at 08:32 -0600, Gary Thomas wrote:
> I had a working build based on
> commit 52295fa3deef3b0374b99829626d524cefae6001
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Wed May 18 00:03:02 2011 +0100
>
> Improve handling of 'all' architecture recipes and their interaction with sstate
>
> Today, I updated to
> commit 484c4e73245c93a08413cd204513bf5c5698b994
> Author: Saul Wold <sgw@linux.intel.com>
> Date: Tue May 31 22:42:49 2011 -0700
>
> clutter-1.6: Add patch to update gettext macro version
>
> Now, it tries to build gettext-native and fails with the log at
> http://www.mlbassoc.com/poky/gettext-native-log.do_compile
> I don't see what's happening here. If I try an identical
> build (same local.conf, etc) in a new tree, it succeeds.
>
> I notice that my old build has git-native built and installed (which based
> on the log is being used?), but the build from scratch does not.
>
> Any ideas?
It looks like gettext now has a dependency on git being present. We need
to add git-native to its DEPENDS, crazy as that may be :/
For a while I thought cvs was required too but it turns out its not,
thankfully.
I'm testing a patch which I'll push shortly.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-02 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 14:32 Problem with gettext-native Gary Thomas
2011-06-02 17:21 ` Richard Purdie [this message]
2011-06-03 0:54 ` Khem Raj
2011-06-03 16:25 ` Gary Thomas
2011-06-03 16:35 ` Mark Hatle
2011-06-03 16:56 ` Gary Thomas
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=1307035303.27470.584.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@yoctoproject.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.