* Andreas Tille <andr...@an3as.eu>, 2014-02-20, 18:04:
dh_auto_test
chmod a+x tests/pysam_test_offline.py
set -e -x;\
for pyv in `pyversions -dv` ; do \
cd tests && env PYTHONPATH=/«PKGBUILDDIR»/build/lib.«ARCH»-${pyv}
./pysam_test_offline.py ; \
done
+ pyversions -dv
+ cd tests
+ env PYTHONPATH=/«PKGBUILDDIR»/build/lib.«ARCH»-2.7 ./pysam_test_offline.py
Traceback (most recent call last):
File "./pysam_test_offline.py", line 8, in <module>
import pysam
ImportError: No module named pysam
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
Obfuscated build logs are not very helpful. :|
Here's an actual build log snippet for i386:
| dh_auto_build
| running build
| running build_py
| creating build
| creating build/lib.linux-i686-2.7
| creating build/lib.linux-i686-2.7/pysam
[...]
| + env
PYTHONPATH=/build/python-pysam-fLMqAQ/python-pysam-0.7.5/build/lib.linux-i486-2.7
./pysam_test_offline.py
| Traceback (most recent call last):
| File "./pysam_test_offline.py", line 8, in <module>
| import pysam
| ImportError: No module named pysam
| make[1]: *** [override_dh_auto_test] Error 1
So setup.py installed stuff to "build/lib.linux-i686-2.7", but
PYTHONPATH is set to "build/lib.linux-i486-2.7".
/usr/share/python/python.mk defines a macro for determining build
directory. You might want to use it. :)
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140220174400.ga9...@jwilk.net
