In trying to build the subject package I ran into a problem. However, there's was a happy ending so I've been left with just a couple of (philosophical?) questions.
Without doing anything, the build (make) would hit me with errors like this: Traceback (most recent call last): File "main/es_generator.py", line 26, in <module> import APIspecutil as apiutil File "/usr/src/Mesa-8.0.1/src/mesa/main/APIspecutil.py", line 28, in <module> import libxml2 ImportError: No module named libxml2 Four in all. Mesa was twice looking for a 'libxml2.py' file and twice for 'libxml2mod.so' (without being too explicit in the latter case; it claimed it found "No module named libxml2mod".) I thought a ".py" is a module and a ".so" is a (shared) library, but that's an aside and what do I know anyway. Luckily, I caught on to what was going on relatively fast and made 'make' finally behave by setting PYTHONPATH=/usr/lib/python2.6/site-packages Whence, two questions 1. One strange: why 'make' wouldn't work with just PYTHONPATH=/usr/lib/python2.6 ? 2. Where did I miss the existence and then the setting of a "PYTHONPATH" ? I do have a "PYTHONDOCS=/usr/share/doc/Python-2.7.2" from the "Python-2.7.2" installation, but evidently I missed the text on and importance of PYTHONPATH somewhere. Any comments will be warmly appreciated. -- Alex -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
