Re: Using SWIG to build C++ extension

2008-07-13 Thread mk
Hello Bas, Thanks, man! Your recipe worked on Debian system, though not on RedHat, and I still have no idea why. :-) Anyway, I have it working. Thanks again. I took your example files and did the following: changed the #include "edit_distance.h" to #include "edit_distance.c" in the edit_dist

Re: Using SWIG to build C++ extension

2008-07-11 Thread Bas Michielsen
mk wrote: > Hello, > > I'm having terrible problems building C++ extension to Python 2.4 using > SWIG. I'd appreciate if somebody knowledgeable at the subject took a > look at it. swig-1.3.29, g++ (GCC) 4.1.1 20070105 (Red Hat 4.1.1-52). > > I used following commands to build C++ extension: > >

Re: Using SWIG to build C++ extension

2008-07-11 Thread mk
And what's infuriating is that the .o files do contain the necessary symbol: # grep _Z13edit_distanceRSsS_ * Binary file edit_distance.o matches Binary file _edit_distance.so matches Binary file edit_distance_wrap.o matches -- http://mail.python.org/mailman/listinfo/python-list

Using SWIG to build C++ extension

2008-07-11 Thread mk
Hello, I'm having terrible problems building C++ extension to Python 2.4 using SWIG. I'd appreciate if somebody knowledgeable at the subject took a look at it. swig-1.3.29, g++ (GCC) 4.1.1 20070105 (Red Hat 4.1.1-52). I used following commands to build C++ extension: # swig -c++ -python edit