From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-2.0-nativesdk: Fix build on ubuntu 11.10
Date: Tue, 31 Jul 2012 12:09:01 +0100 [thread overview]
Message-ID: <1343732941.9526.5.camel@ted> (raw)
In-Reply-To: <1343717699-23305-1-git-send-email-raj.khem@gmail.com>
On Mon, 2012-07-30 at 23:54 -0700, Khem Raj wrote:
> When you have a distro which has older version of
> glib-2.0 installed then it does not have compile_resources
> installed which essentially glib-2.0 nativesdk is
> looking for on build host. So like in a cross build
> we disable the configure check which will force it
> to build an internal copy and use it.
>
> This problem may not be seen on newer distros like
> ubuntu 12.04 since they have newer version of glib-2.0
> installed
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-core/glib-2.0/glib-2.0_2.32.4.bb | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-07-31 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 6:54 [PATCH] glib-2.0-nativesdk: Fix build on ubuntu 11.10 Khem Raj
2012-07-31 11:09 ` 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=1343732941.9526.5.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