Re: Python & libxml2/libxslt/gamin

[Kenneth Murray <kmurray eskimo com>]

> Did you modify gar.conf.mk to explicitly use your new version of Python?
> 
> I am running YDL-4.0.1, which also comes with Python2.3.  I built and
> installed 2.4.1 under /opt.  I have modified gar.conf.mk as follows
> 
>         # If you want to use a different version of python everywhere
>         # change this
>         # PYTHON = $(shell which python)
>         PYTHON = /opt/python-2.4.1/bin/python
> 
> With this modification libxml2, libxslt, and gamin build for both
> garnome-2.12.2.1 and garnome-2.13.4.
> 
> To get the applications to run with the correct python site-packages, I
> export PYTHONPATH in garnome-session
> 
>         [ignore line wrap]
>         PYTHONPATH=$GARNOME/lib/python2.4/site-packages:$GARNOME/lib/python2.4/site-packages/gtk-2.0
> 
> where $GARNOME is the root of the garnome install tree on my system.
> 

Yup, I've got the PYTHONPATH thing in my garnome-session.

I didn't edit gar.conf.mk to explicitly use my new Python, but the shell
code in there picks it up automatically because I installed the new
Python in /usr/local/bin, and that's in my PATH.

What happens is that the libxml2 configure script finds the new Python
but misses the headers (configure output follows):

checking for isnan... yes
checking for isinf... yes
Found python in environment PYTHON=/usr/local/bin/python
Found Python version 2.4
could not find python2.4/Python.h
checking for shl_load in -ldld... no
checking for dlopen in -ldl... yes

The libxml2 compile runs normally, it just doesn't build or install the
Python stuff. On the other hand, if I delete /usr/local/bin/python,
libxml2 happily builds and installs everything, because it
finds /usr/bin/python (version 2.3), *and* it finds the headers. Bottom
line, the code in configure.in fails to handle Python installed in a
non-standard directory.

The same comments apply for libxslt and gamin; their builds don't fail
entirely, just the python parts.

Does the patch I sent work for you (or at least fail to wreck your
working setup)?

Regards,

Kenneth