From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: shared-mime-info fails to build if intltool-native is present
Date: Mon, 10 Oct 2011 13:55:47 +0100 [thread overview]
Message-ID: <1318251360.23801.29.camel@ted> (raw)
In-Reply-To: <3641B9F4-58D3-4AA1-B3D8-A08C57A97A11@dominion.thruhere.net>
On Sun, 2011-10-09 at 16:34 +0200, Koen Kooi wrote:
> I finally tracked down the cause of the intermittent shared-mime-info
> build failures I was seeing. No patch yet, but now you all know what's
> causing it :)
Try the patch I just sent to the list ;-)
Cheers,
Richard
prev parent reply other threads:[~2011-10-10 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 14:34 shared-mime-info fails to build if intltool-native is present Koen Kooi
2011-10-10 12:55 ` 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=1318251360.23801.29.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox