From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] [PATCH 0/3] mesa upgrade
Date: Wed, 4 Jun 2014 19:12:20 +0200 [thread overview]
Message-ID: <20140604171220.GT2426@jama> (raw)
In-Reply-To: <CAJTo0Lab7wwV2NN=NSMqLYTxeW=_CfeGwvETkDCh4emwVRLxFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Wed, Jun 04, 2014 at 03:24:34PM +0100, Burton, Ross wrote:
> On 4 June 2014 13:52, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Sorry for hi-jacking the thread, but since today even the older 9.2.5 is
> > failing to find native python-libxml2
> >
> > config.log:
> > configure:8059: checking for python2
> > configure:8075: found
> > /OE/build/oe-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/python-native/python2
> > configure:8086: result: python2
> > configure:8103: checking python2 module: libxml2
> > configure:8112: result: no
> > configure:8118: error: failed to find required module libxml2
> >
> > Any idea why it started to fail now?
>
> Great. Can you share the config.log?
This is from config.log, do you want whole file?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-06-04 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:59 [PATCH 0/3] mesa upgrade Valentin Popa
2014-05-13 14:59 ` [PATCH 1/3] dri3proto: add it to oe-core Valentin Popa
2014-05-13 14:59 ` [PATCH 2/3] libxshmfence: " Valentin Popa
2014-05-13 14:59 ` [PATCH 3/3] mesa: upgrade to 10.1.3 Valentin Popa
2014-05-16 17:19 ` Saul Wold
2014-05-19 15:06 ` Valentin Popa
2014-05-19 15:02 ` Saul Wold
2014-05-13 15:28 ` [PATCH 0/3] mesa upgrade Burton, Ross
2014-05-14 20:34 ` [oe] " Otavio Salvador
2014-06-04 12:52 ` Martin Jansa
2014-06-04 14:24 ` Burton, Ross
2014-06-04 17:12 ` Martin Jansa [this message]
2014-06-06 16:15 ` Burton, Ross
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=20140604171220.GT2426@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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