|
From: Alexander B. <ale...@gm...> - 2006-01-27 18:13:06
|
Numpy-discussion list rejected an attachment. Here are a few relevant lines from the log: In file included from numpy/core/src/multiarraymodule.c:65: numpy/core/src/arrayobject.c: In function `PyArray_FromDimsAndDataAndDescr'= : numpy/core/src/arrayobject.c:766: `intp' undeclared (first use in this func= tion) numpy/core/src/arrayobject.c:766: parse error before ')' token In file included from numpy/core/src/multiarraymodule.c:65: numpy/core/src/arrayobject.c: At top level: numpy/core/src/arrayobject.c:822: parse error before "intp" numpy/core/src/arrayobject.c:822: warning: function declaration isn't a prototype numpy/core/src/arrayobject.c: In function `PyArray_Scalar': numpy/core/src/arrayobject.c:841: `Bool' undeclared (first use in this func= tion) numpy/core/src/arrayobject.c:841: parse error before ')' token numpy/core/src/arrayobject.c:841: parse error before ')' token numpy/core/src/arrayobject.c:841: warning: left-hand operand of comma expression has no effect ---------- Forwarded message ---------- From: Sasha <nd...@ma...> Date: Jan 27, 2006 12:33 PM Subject: Re: [Numpy-discussion] Numpy does not compile with PY_ARRAY_TYPES_PREFIX To: Andrew Straw <str...@as...>, numpy-discussion <num...@li...> I've just updated to svn r2006. Regular build works fine, but $ CFLAGS=3D-DPY_ARRAY_TYPES_PREFIX=3DPyArray_NS_ python setup.py build produced the attached log. Note that I am not compiling any extention, just regular numpy. On 1/27/06, Andrew Straw <str...@as...> wrote: > Sasha wrote: > > >I have attempted to compile RPy (see http://rpy.sourceforge.net/) with > >numpy and found that both R and numpy headers define Int32: > > > >.../numpy/core/include/numpy/arrayobject.h:304: conflicting types for `I= nt32' > >.../lib/R/include/R_ext/Random.h:57: previous declaration of `Int32' > > > >I have tried to fix the problem by setting PY_ARRAY_TYPES_PREFIX as foll= ows: > > > >$ CFLAGS=3D-DPY_ARRAY_TYPES_PREFIX=3DPyArray_NS_ python setup.py build > > > >This resulted in compile error in almost every Numpy source file. > > > >Am I using PY_ARRAY_TYPES_PREFIX correctly? If not, what is the > >recommended way to solve name conflicts involving Numpy typoes? > > > > > > David Cooke informed me some time ago that the #include > "numpy/arrayobject.h" line should go _after_ the other #includes. It's > worked for me well enough ever since, although it seems rather fragile. > Otherwise I'm not having the same issue with current svn. There was an > issue with release 0.9.4 for C++ code, anyway. > > Cheers! > Andrew > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |