Bugzilla – Bug 31598
configure: Doesn't check for python libxml2
Last modified: 2013-01-24 10:50:56 UTC
My build in a (quite minimal) chroot broke with:
make: Entering directory `/home/kibi/mesa/mesa/src/mesa'
python -t -O -O main/es_generator.py -S main/APIspec.xml -V GLES1.1 > main/api_exec_es1.c
Traceback (most recent call last):
File "main/es_generator.py", line 26, in <module>
import APIspecutil as apiutil
File "/home/kibi/mesa/mesa/src/mesa/main/APIspecutil.py", line 28, in <module>
ImportError: No module named libxml2
I guess you may want to add a check on the availability of this module in configure.ac?
Fixed by commit 410b58c7bfcebbc866d2dc4ab32c6f23b55d383b
On systems where 'python' is 3.x and 'python2' is 2.x, mesa's config will store the variable PYTHON2='python2', whereas your code checks the PYTHON variable, which is unset , and always uses 'python' (3.x), which can't have libxml2. This causes the build to fail even with everything available.
Created attachment 73402 [details] [review]
use correct version of python to make the check
The attached patch fixes the check on systems where python2 is not the default.
build also failed on archlinux, where python 3.x is default.
I use a simple workaround for now :
PYTHON='python2' ./autogen.sh --prefix=/usr /
Please reopen this bug
fixed with this commit :
build: Fix build on systems where /usr/bin/python isn't python 2.