clearsilver 0.10.2 does not work with python 2.5. I bumped it to 0.10.3 and patched it to work:
- its configure.in contains a hardcoded list of python versions, to which I added 2.5 (and 2.6 while I was at it). But see bug 144580, it would probably be better to fix that one instead.
- it calls PyMem_DEL to free things allocated with PyObject_NEW. This has always been invalid but only actually stopped working in python 2.5.
This should probably go upstream as well but I have not found upstreams bug tracker yet. If someone else does please put the patch on there or tell me where it is. If this bug is fixed in portage before someone finds their bug tracker I will inform upstream through email.
Created attachment 97901 [details, diff]
configure.in and PyMem/PyObject fixes.
Created attachment 98010 [details]
ebuild including this patch
Hmm I've created an ebuild which includes this patch but it does not compile module for python 2.5 but for 2.4... I put this as an attachment so you can check if I did something wrong.
The patch touches configure.in, so you will have to rerun at least autoconf for it to work. Adding "inherit autotools" and running "eautoreconf" at the end of src_unpack should do the trick.
I'll report it to upstream, and I'll include some patches into clearsilver-0.10.3 asap.
(In reply to comment #3)
> The patch touches configure.in, so you will have to rerun at least autoconf for
> it to work. Adding "inherit autotools" and running "eautoreconf" at the end of
> src_unpack should do the trick.
It works almost perfectly, clearsilver compiles now with python 2.5, but puts *.so in / instead of python2.5/site-packages, I do not know autotools very well so I dont know why...
That does not happen here. Can you provide a build log? config.log might also be interesting.
Created attachment 98145 [details]
Created attachment 98147 [details]
PYTHON_SITE is not set...
Huh. I do not see how that could happen unless PYTHON_SITE is set to the empty string in your (or really portage's) environment. Can you check if that happened somehow? As far as I can tell the configure script should always set PYTHON_SITE to something else than the empty string unless it's already set in the environment.
Ok. I changed my ebuild to compile 10.3 version and it works. In changelog from 10.2 to 10.3 they write that:
Change 2006/01/26 by blong@blong
Fix bug introduced in 0.10.2 version of configure (bad sh syntax
for PYTHON_SITE) and try another tact for getting site locations
that should work with /usr/lib64 variations.
Please test clearsilver-0.10.3.
(In reply to comment #11)
> Please test clearsilver-0.10.3.
Works fine. :)