|
From: Sasha <nd...@ma...> - 2006-01-28 02:12:24
|
Thanks for your advise. With the help of -E option, I've found the problem. I was using the version of the header that used uint in the C-API. the problem was fixed in svn r1983:=20 http://projects.scipy.org/scipy/numpy/changeset/1983 . -- sasha On 1/27/06, Travis Oliphant <oli...@ee...> wrote: > Travis Oliphant wrote: > > > Sasha wrote: > > > >> On 1/27/06, David M. Cooke <co...@ph...> wrote: > >> > >> > >>> You need to add #include "Python.h" as the first include (and add a > >>> -I<python include directory> to your gcc line, of course). > >>> > >> > >> > >> Still does not work > >> > >> > > It works for me. Try the attached file. > > > > gcc -I /usr/include/python2.4 -I > > /usr/lib/python2.4/site-packages/numpy/core/include -c test.c > > > > Worked fine. > > > > Maybe Python.h has to come *before* the special #define. > > On my system, it didn't seem to matter. All incarnations worked. > Perhaps there is something wrong with your installation. Could you > show the very first errors you are getting. Is the wrong header being > picked up from somewhere. > > Also perhaps you could look at the output of the compilation using the > -E (pre-processor only) flag. This might help nail down the problem. > > -Travis > > > > ------------------------------------------------------- > 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 > |