On 14/05/07 at 09:58 -0400, Adam C Powell IV wrote: > severity 423794 normal > thanks > > On Mon, 2007-05-14 at 11:09 +0200, Jérémy Bobbio wrote: > > Package: pysparse > > Version: 1.0-1 > > Severity: serious > > Justification: no longer builds from source > > > > Hi! > > > > pysparse currently fails to build from source in sid [1]: > > > > --- 8< --- > > running build_ext > > building 'pysparse.spmatrix' extension > > creating build/temp.linux-i686-2.5 > > creating build/temp.linux-i686-2.5/Src > > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes > > -fPIC -IInclude -I/usr/include/python2.5 -c Src/spmatrixmodule.c -o > > build/temp.linux-i686-2.5/Src/spmatrixmodule.o > > Src/spmatrixmodule.c:13:37: error: Numeric/arrayobject.h: No such file or > > directory > > In file included from Src/spmatrixmodule.c:24: > > Src/ll_mat.c: In function 'LLMat_matvec_transp': > > Src/ll_mat.c:763: error: 'PyArrayObject' undeclared (first use in this > > function) > > Src/ll_mat.c:763: error: (Each undeclared identifier is reported only once > > [...] > > error: command 'gcc' failed with exit status 1 > > make: *** [stamp-build-2.5] Error 1 > > --- >8 --- > > That's odd. Sounds like something major changed in python-numeric, > since its header file is missing... no, unstable still has 24.2-7 like > etch.
Yes, but 24.2-7 doesn't include the header file for python 2.5. > Have you tried rebuilding python-numeric with python 2.5, then building > pysparse? I notice that python-numeric does not appear in > http://people.debian.org/~lucas/logs/2007/05/13/ , nor in any other > subdir of http://people.debian.org/~lucas/logs/2007/ , so it seems not. if it's not here, it just means that it never failed. > I see. This is a problem with the new python build system: it's hard to > tell which packages have been built with which version of python. > There's no reason for me to change my python-numeric dependency, but no > way for any build system to tell whether the same python-numeric package > has been built for the new python. > > Reclassifying this as normal. If you can show that you built its python > dependencies with 2.5, and then this failed, then I will agree that it > is a bug in pysparse. I'm not really a python expert. :-) But why did your package suddenly start to build python 2.5 files as well ? -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
