Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Darren Hart <dvhart@linux.intel.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] shared-mime-info: add libxml-parser-perl to DEPENDS
Date: Thu, 22 Sep 2011 13:03:38 -0700	[thread overview]
Message-ID: <4E7B949A.8050407@linux.intel.com> (raw)
In-Reply-To: <1316721518.28323.1.camel@ted>

On 09/22/2011 12:58 PM, Richard Purdie wrote:
> On Thu, 2011-09-22 at 11:49 -0700, Darren Hart wrote:
>> Fixes [YOCTO #1514]
>>
>> Building core-image-minimal on qemuppc (and likely others) can fail in
>> the shared-mime-info configure step with the following error:
>>
I was thinking about this and went "why is shared-mime-info even in 
core-image-minimal", are you sure that was the image you were building. 
This might point to some other problem also.

Sau!

>> checking for XML::Parser... configure: error: XML::Parser perl module is
>> required for intltool
>>
>> Adding libxml-parser-perl to DEPENDS allows share-mime-info-native to build
>> successfully.
>>
>> Testing: build tested the native version on qemuppc. I run into tool chain
>> build failures before I can get to building the target version.
>>
>> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
>> CC: Joshua Lock<josh@linux.intel.com>
>> ---
>>   .../shared-mime-info/shared-mime-info.inc          |    4 ++--
>>   1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/recipes-support/shared-mime-info/shared-mime-info.inc b/meta/recipes-support/shared-mime-info/shared-mime-info.inc
>> index 64eef9d..e206305 100644
>> --- a/meta/recipes-support/shared-mime-info/shared-mime-info.inc
>> +++ b/meta/recipes-support/shared-mime-info/shared-mime-info.inc
>> @@ -5,8 +5,8 @@ SECTION = "base"
>>   LICENSE = "GPLv2+"
>>   LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3"
>>
>> -DEPENDS = "libxml2 intltool-native glib-2.0 shared-mime-info-native"
>> -DEPENDS_virtclass-native = "libxml2-native intltool-native glib-2.0-native"
>> +DEPENDS = "libxml2 intltool-native glib-2.0 shared-mime-info-native libxml-parser-perl"
>> +DEPENDS_virtclass-native = "libxml2-native intltool-native glib-2.0-native libxml-parser-perl-native"
>>
>>   SRC_URI = "http://freedesktop.org/~hadess/shared-mime-info-${PV}.tar.bz2"
>
>
> There must be some underlying problem here. intltool-native should
> depend on libxml-parser-perl-native so it should already be built. We
> need to fix the underlying issue, not the symptom :/
>
> Cheers,
>
> Richard
>
>



  reply	other threads:[~2011-09-22 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 18:49 [PATCH 0/1] shared-mime-info: add libxml-parser-perl to DEPENDS Darren Hart
2011-09-22 18:49 ` [PATCH 1/1] " Darren Hart
2011-09-22 19:58   ` Richard Purdie
2011-09-22 20:03     ` Saul Wold [this message]
2011-09-22 20:19       ` Darren Hart
2011-09-22 20:53         ` Richard Purdie
2011-09-22 20:32       ` Darren Hart
2011-09-22 20:27     ` Darren Hart
2011-09-22 20:34       ` Koen Kooi
2011-09-22 20:52       ` Richard Purdie

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=4E7B949A.8050407@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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