On 7/24/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Paul Barrett wrote:
> > I'm having a problem converting a C extension module that was
> > originally written for numarray to use numpy.  I using swig to create
> > a wrapper flle for the C code.  I have added the
> > numpy.get_numarray_include() method to my setup.py file and have
> > changed the numarray/libnumarray.h to use numpy/libnumarray.h.  The
> > extension appears to compile fine (with the exception of some warning
> > messages).  However, when I import the module, I get a segfault.  Do I
> > need to add anything else to the share library's initialization step
> > other than import_libnumarray()?
> >
>
> No, that should be enough.   The numarray C-API has only been tested on
> a few extension modules.  It's very possible some of the calls have
> problems.
>
> It's also possible you have an older version of numpy lying around
> somewhere.   Do you get any kind of error message on import?

No. I'm using a recent SVN version of numpy and I remove the install
and build directories before every new build, i.e. I do clean build
after each SVN update.

No.  Just the segfault.  I guess the best thing to do is put in print
statements and try to locate where it fails.

Thanks for the clarification, Travis.

 -- Paul

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Reply via email to