From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/6] libxml2: fix python path and add libxml2-python
Date: Wed, 15 Apr 2015 21:38:42 +0100 [thread overview]
Message-ID: <1429130322.6976.154.camel@linuxfoundation.org> (raw)
In-Reply-To: <39bde4872c0287e3617e2e8af5768903e1d33cfc.1429002519.git.liezhi.yang@windriver.com>
On Tue, 2015-04-14 at 02:08 -0700, Robert Yang wrote:
> We have libxml2-python for native and nativesdk, but don't have it for
> target, and can't find the reason from the git log, libxml2-python is
> widely used, after looked into it's configure.in, we can add it
> by PACKAGECONFIG.
>
> The previous --with-python=${STAGING_BINDIR}/python is incorrect, it
> acted as work becase it's conigure can check automatically, python is in
> ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN}, as known as
> ${PYTHON}.
>
> Add python to PACKAGECONFIG, since createrepo rdepends on
> libxml2-python, otherwise the target createrepo can't work.
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Something here caused a load of failures:
http://errors.yoctoproject.org/Errors/Search/?items=10&query=90b8d406488b0a3c42b2a745526e5b1273d8a982
e.g. specifically http://errors.yoctoproject.org/Errors/Details/9808/
Cheers,
Richard
next prev parent reply other threads:[~2015-04-15 20:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 9:08 [PATCH 0/6] meta: 6 fixes Robert Yang
2015-04-14 9:08 ` [PATCH 1/6] libxml2: fix python path and add libxml2-python Robert Yang
2015-04-15 20:38 ` Richard Purdie [this message]
2015-04-16 8:32 ` Robert Yang
2015-04-14 9:08 ` [PATCH 2/6] cracklib: add python support back Robert Yang
2015-04-14 9:09 ` [PATCH 3/6] libepoxy: DEPENDS on virtual/mesa Robert Yang
2015-04-14 13:50 ` Andreas Müller
2015-04-14 13:52 ` Burton, Ross
2015-04-14 14:03 ` Andreas Müller
2015-04-14 14:06 ` Burton, Ross
2015-04-14 15:47 ` Andreas Müller
2015-04-15 1:44 ` Robert Yang
2015-04-15 8:28 ` Jussi Kukkonen
2015-04-15 8:36 ` Burton, Ross
2015-04-15 8:32 ` Burton, Ross
2015-04-15 9:30 ` Robert Yang
2015-04-15 9:37 ` Burton, Ross
2015-04-15 10:21 ` Robert Yang
2015-04-15 16:00 ` Burton, Ross
2015-04-15 17:27 ` Andreas Müller
2015-04-15 19:08 ` Burton, Ross
2015-04-15 20:06 ` Andreas Müller
2015-04-14 9:09 ` [PATCH 4/6] strace: fix build for aarch64 Robert Yang
2015-04-14 9:09 ` [PATCH 5/6] aspell: inherit binconfig-disabled Robert Yang
2015-04-14 9:09 ` [PATCH 6/6] libunwind: fix build with aarch64 Robert Yang
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=1429130322.6976.154.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--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