From: jhuang0 <jackie.huang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] glib-2.0: inherit pythonnative
Date: Wed, 10 Jul 2013 10:12:46 +0800 [thread overview]
Message-ID: <51DCC31E.4020505@windriver.com> (raw)
In-Reply-To: <CAJTo0LbLGKEea1vfcQH19JU++mTViDeZ2CSyLu3Cof2wqEYcMQ@mail.gmail.com>
On 7/9/2013 10:56 PM, Burton, Ross wrote:
> On 8 July 2013 04:25, <jackie.huang@windriver.com> wrote:
>> glib-2.0 needs to inherit pythonnative because it depends on
>> python-native. This has caused problems on SLED11.2 if no
>> python-xml installed.
>
> I just built glib-2.0 from scratch without python-native being
> present, so can you justify this please?
The problem happened on a SUSE host without python-xml installed, Robert
just told me that it has been taken care of by:
commit bb027a332f2f2927a6bcbc4c035b42a012d0579e
Author: Jesse Zhang <sen.zhang@windriver.com>
Date: Mon Jun 3 07:37:48 2013 +0000
sanity.bbclass: make sure python is a full install
Components of the Standard Library should be available. Add a sanity
check for xml.parsers.expat; we might add more in the future.
[YOCTO #4424]
Signed-off-by: Jesse Zhang <sen.zhang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Thanks,
Jackie
>
> Ross
>
--
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745
next prev parent reply other threads:[~2013-07-10 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 3:24 [PATCH 0/1] glib-2.0: inherit pythonnative jackie.huang
2013-07-08 3:25 ` [PATCH 1/1] " jackie.huang
2013-07-09 14:56 ` Burton, Ross
2013-07-10 2:12 ` jhuang0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-01 8:53 [PATCH 0/1] " Xin Ouyang
2012-11-01 8:53 ` [PATCH 1/1] " Xin Ouyang
2012-11-01 11:45 ` 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=51DCC31E.4020505@windriver.com \
--to=jackie.huang@windriver.com \
--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.