[Numpy-discussion] bdist_rpm failure

Travis Oliphant oliphant.travis at ieee.org
Tue Jul 11 20:24:01 CDT 2006


Christian Kristukat wrote:
> Hi,
> currently the bdist_rpm build method seems to be quite unstable. It works for
> some recent svn revisions, for the current 2804, however, not.
> The error messages begin with:
>
> building 'numpy.core.multiarray' extension
> compiling C sources
> C compiler: gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=i586
> -mtune=i686 -fmessage-length=0 -Wall -
> D_FORTIFY_SOURCE=2 -g -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
> -D_FORTIFY_SOURCE=2 -fPIC
>
> creating build/temp.linux-i686-2.4
> creating build/temp.linux-i686-2.4/numpy
> creating build/temp.linux-i686-2.4/numpy/core
> creating build/temp.linux-i686-2.4/numpy/core/src
> compile options: '-Ibuild/src.linux-i686-2.4/numpy/core/src -Inumpy/core/include
> -Ibuild/src.linux-i686-2.4/n
> umpy/core -Inumpy/core/src -Inumpy/core/include -I/usr/include/python2.4 -c'
> gcc: numpy/core/src/multiarraymodule.c
> numpy/core/src/multiarraymodule.c:24:28: error: numpy/noprefix.h: No such file
> or directory
> numpy/core/src/multiarraymodule.c:33: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘*’ toke
> n
>
>   
Make sure you get rid of the MANIFEST file in the source directory 
before trying to run sdist or bdist_rpm. The MANIFEST file is not being 
deleted when it is dated...

-Travis





More information about the Numpy-discussion mailing list