Hi, this one is "funny". setuptools uses python's os.uname() to check which arch it is running on, and where the temp-build-path is. This fails nicely on machines with 64bit-kernel and 32bit-userland (at least amd64, as it has x86_86 in uname, as the kernel is for x86_64).
In this particular bug, it's not 64 vs 32 bit, but i686 vs i486, quoting the build-log: > g++ -pthread -shared -Wl,-Bsymbolic-functions -g -O2 build/temp.linux-i686-2.6/src/wrapper/wrap_cl.o build/temp.linux-i686-2.6/src/wrapper/wrap_cl_part_1.o build/temp.linux-i686-2.6/src/wrapper/wrap_cl_part_2.o build/temp.linux-i686-2.6/src/wrapper/wrap_constants.o -lboost_python-py26 -lOpenCL -o build/lib.linux-i686-2.6/pyopencl/_cl.so > PYTHONPATH=../build/lib.linux-i486-2.6/ /usr/bin/make -C doc html the stuff is built in build/lib.linux-i686-2.6/, but PYTHONPATH is set to build/lib.linux-i486-2.6/. This is done in debian/rules: PYTHONPATH=../build/lib.$(DEB_BUILD_ARCH_OS)-$(DEB_BUILD_GNU_CPU)-$(firstword $(PYVERS)) $(DEB_BUILD_GNU_CPU) is wrong here, as is expands correctly to i486 (even on amd64 kernel with a i386 chroot). Looking at dpkg-architecture on in my 32bit chroot r...@nana:/# dpkg-architecture DEB_BUILD_ARCH=i386 DEB_BUILD_ARCH_OS=linux DEB_BUILD_ARCH_CPU=i386 DEB_BUILD_ARCH_BITS=32 DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_CPU=i486 DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=i486-linux-gnu DEB_HOST_ARCH=i386 DEB_HOST_ARCH_OS=linux DEB_HOST_ARCH_CPU=i386 DEB_HOST_ARCH_BITS=32 DEB_HOST_ARCH_ENDIAN=little DEB_HOST_GNU_CPU=i486 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_HOST_GNU_TYPE=i486-linux-gnu r...@nana:/# uname -a Linux nana 2.6.34-1-amd64 #1 SMP Sun Jun 6 22:29:25 UTC 2010 x86_64 GNU/Linux there is no way to find x86_64 here, so I think this is the same for i686 (or should DEB_HOST_GNU_CPU be x86_64 and it's a bug in dpkg?). I fear we have to "parse" `uname -m` here, to fix that issue and match setuptools' algorithm. Regards Evgeni Golov -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
