From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] mesa3d: "ImportError: No module named libxml2"
Date: Mon, 12 Nov 2012 22:06:07 +0100 [thread overview]
Message-ID: <50A164BF.7080603@mind.be> (raw)
In-Reply-To: <50A0E402.1050805@carallon.com>
On 11/12/12 12:56, Will Wagner wrote:
> I ported newer X11 to buildroot a while back a posted a link to the repository. At the time the only comment I got was
> from Thomas about the requirement for python/libxml2 which he hated then as well :)
>
> I patched it so that it conditionally build host-libxml2 with the reuqired support if mesa3d was selected. My patch for
> this is at https://gitorious.org/willw-buildroot/willw-buildroot/commit/421b4fd572869b22de11a0f0fad161e284c41bcc
>
> If we want newer mesa3d support I think we are going to have to come up with some suitable solution for this.
Yes, and your patch looks in pretty good shape already. I would make
BR2_PACKAGE_HOST_LIBXML2_PYTHON a blind option (i.e. remove the string after
bool). I'd also remove the dependency on BR2_PACKAGE_LIBXML2 (in fact,
mesa3d doesn't require libxml2). And I'd keep the --without-debug. But
otherwise the patch looks good :-)
Care to post it to the list, followed by a mesa3d patch that uses it?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-11-12 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 9:18 [Buildroot] mesa3d: "ImportError: No module named libxml2" Vellemans, Noel
2012-11-05 9:38 ` Maxime Ripard
2012-11-10 1:51 ` Arnout Vandecappelle
2012-11-12 11:39 ` Vellemans, Noel
2012-11-12 11:56 ` Will Wagner
2012-11-12 21:06 ` Arnout Vandecappelle [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=50A164BF.7080603@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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