On 01/03/14 20:47, Nathan Scott wrote:
----- Original Message -----
Platform - Linux Mint 12 Lisa
...
On this platform, python-all-dev pulls in BOTH python 2.6 and 2.7
...
Can someone who understand how the python build and packaging works please
investigate?
What does "pyversions -vr" say (needs to be run from top-level of the source
tree, oddly enough)? This output is used to drive the build process (from
debian/rules, line ~160)
for V in $(shell pyversions -vr); do \
$(pkgpcp_python) $(MAKE) PYTHON=python$$V -C src/python install; \
done
I am seeing this one two systems now ...
Linux Mint 12 (vm18)
kenj@vm18:~/src/pcp$ pyversions -vr
2.7 2.6
Debian 7.4 (vm21)
kenj@vm21:~/src/pcp$ pyversions -vr
2.7 2.6
And from Logs/pcp I see lines like
for V in 2.7 2.6; do \
export GZIP=-9q DIST_ROOT=`pwd`/debian/python-pcp;
/usr/bin/make PYTHON=python$V -C src/python install; \
done
I think the problem is that the first make leaves 2.7 turds behind that
are not remade for 2.6 ... adding /usr/bin/make -C src/python clean
after the make install seems to fix this, but I don't know if that
leaves the tree in a bozo state, and this sort of hack cannot possibly
work for some other builds, like for tarball packaging.
It seems like you need to clone src/python for each version of Python
that you want to build for, and descend into each of these in turn at
each step in the build.
|