On 07/03/13 08:28, Nathan Scott wrote:
----- Original Message -----
On 06/03/13 20:15, Nathan Scott wrote:
On vm18 3.6.11 x86_64 LinuxMint 12 (lisa) the build dies a
horrible
death in the python code with ...
I *think* this is from pyversions -nr returning more versions of
python than are installed on the machine. I think in turn this
is because the build dependency is not ensuring python2.6 is there.
I've attempted a fix: dev b8f72f3 not 100% certain though - seems
like it might work.
OK this is more broken than I thought ... pyversions -vr (no -n)
returns as follows:
Not sure if you got this bit figured, but apparently you must run
that command from with a work area:
nathans@verge:/source/git/pcp$ pyversions -vr
2.7 2.6
nathans@verge:/source/git/pcp$ cd src/
nathans@verge:/source/git/pcp/src$ pyversions -vr
pyversions: error parsing Python-Version attribute
nathans@verge:/source/git/pcp/src$ cd ..
nathans@verge:/source/git/pcp$ grep Python-Version debian/control
X-Python-Version: >= 2.6
So, with my change from yesterday I was expecting you'd get an
unsatisfied build dependency (thanks to the "python-all" req),
and once you install "python2.6" alongside your "python2.7" it
would magically start to work.
I changed pyversion -vr to pyversion -i which seems more correct in
debian/rules ... do you agree?
Then I installed python-all on LinuxMint (and added yet more mystical
spells to my check-vm script to catch this in future), but Makepkgs is
now complaining thusly
== dpkg-buildpackage: binary-arch
warning: install_lib: 'build/lib.linux-x86_64-2.6' does not exist -- no
Python modules to install
readelf: Error:
debian/python-pcp/usr/lib/python2.6/dist-packages/pmapi.so: Failed to
read file's magic number
I checked and _both_ python2.6 and python2.7 are installed.
Based on total ignorance, I checked the -dev pkgs and 2.7 is installed
but not 2.6, so I did
# apt-get install python-dev-all
and ran Makepkgs again. Same result.
Reverted my debian/rules changes, ran make clean; Makepkgs again. Same
result.
Nothing more I can add here ... over to you I'm afraid.
|