-   Linux From Scratch (
-   -   Problems compiling MesaLib on 64-bit CLFS System (

EnigmaticFellow 11-20-2012 07:14 AM

Problems compiling MesaLib on 64-bit CLFS System
Posting this on a CLFS system using lynx may be a bit weird for me, but this is pretty much the only way for me to get the compilation error I got without chrooting from another system.

Here's the error message I got when attempting to compile MesaLib:

make[2]: Entering directory `/sources/Mesa-7.9-64/src/mesa'
python -t -O -O main/ -S main/APIspec.xml -V GLES2.0 > main/api_exec_es2.c
Traceback (most recent call last):
  File "main/", line 26, in <module>
    import APIspecutil as apiutil
  File "/sources/Mesa-7.9-64/src/mesa/main/", line 28, in <module>
    import libxml2
ImportError: No module named libxml2
make[2]: *** No rule to make target `main/api_exec_es2.c', needed by `depend'.  Stop.
make[2]: Leaving directory `/sources/Mesa-7.9-64/src/mesa'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/sources/Mesa-7.9-64/src'
make: *** [default] Error 1

So the problem seems to come from the libxml2 module not being defined on python. I do have libxml2 installed on my system, so how would I fix this problem?

druuna 11-20-2012 07:39 AM

You mention installing libxml2, but have you seen these notes (Mesalib):

The libxml2 Python module must have been built during the installation of libxml2 or else MesaLib build will fail.
and (libxml2)

Some packages which utilize libxml2 (such as GNOME Doc Utils) need the Python module installed to function properly and some packages (such as MesaLib) will not build properly if the Python module is not available.
Which would make python a required dependency for libxml2 and not a recommended one.

stoat 11-20-2012 09:26 AM

Even though Python is considered optional for libxml2, it's almost not possible to build libxml2 without Python unless a bigger mistake was already made (IMO). Since xcb-proto requires Python, and since libxcb (next after xcb-proto) requires libxslt which in turn requires libxml2, then libxml2 will be built with Python when that sequence of events happens. It does for me anyway.

There are some circular dependencies with Python, Tk, and X that are irritating. I have been dealing with that by installing Python once with none of its optional packages for xcb-proto, and then a second time with all (almost) of its dependencies after X is done.

EnigmaticFellow 11-20-2012 11:11 AM

Well, attempting to get X on my CLFS system seems to be getting me more and more annoyed with the likes of Python and libxml2. I guess I'll go look at the compilation options I enabled for those two and see if I can tinker with them to get the module right.

Thanks for the help so far, guys.

stoat 11-20-2012 12:17 PM

Yeah, X is a giant thing to install IMO. Things in the book are constantly changing for it, too. My current system has Xorg-7.7 like the current book version, but still I noticed some package version changes since I last installed it in September.

FWIW, I had no big issues when I installed my current version. My notes say the folder gets named wrong for the llvm docs, and I just edited the Makefile for it. Somebody has filed a ticket at the wiki about that. I also added a couple of extra Xorg Applications that the book has dropped but I still need. But that's it. Unless something else big has changed, I would expect X to be clear sailing. A lot to do, but no problems. If you have some way to back up and go at it again, maybe something simple was overlooked or botched. A tarball backup made just before starting X would be really nice.

EnigmaticFellow 11-21-2012 01:57 PM

After recompiling a few libraries, I finally got MesaLib to compile and install onto my system.

driftingblues 03-14-2013 01:49 AM

Hi EnigmaticFellow,

Please tell me how did you solve the libxml2 and python dependencies and compile MesaLib ?

All times are GMT -5. The time now is 04:29 AM.