On Fri, May 27, 2011 at 12:45 PM, Ned Deily wrote:
>
> The discussion in http://bugs.python.org/issue4434 might be of some help.
Thanks Ned! That was most helpful. I'm still not sure exactly what I
changed, but between building with --enable-shared and some fiddling
with how I link my program, I'
In article ,
Chris Angelico wrote:
> Still trying to sort this out, trying various things. If I configure
> --enable-shared, I get a different ImportError: 'libpython3.3m.so.1.0:
> cannot open shared object file: No such file or directory'. That file
> exists in ~/cpython, but sudo make install d
Still trying to sort this out, trying various things. If I configure
--enable-shared, I get a different ImportError: 'libpython3.3m.so.1.0:
cannot open shared object file: No such file or directory'. That file
exists in ~/cpython, but sudo make install doesn't put it anywhere
else. Pointing LD_LIBR
Followup. I'm now using Python 3.3 straight from Mercurial, and am
seeing the same issues. I've managed to get the compilation step to
succeed by naming the library for full inclusion and adding -lutil
-ldl (sounding rather Donizetti there), and my program runs. However,
it's unable to import all i
I'm starting to feel incredibly stupid here. Hopefully someone can
point out a really obvious thing that I've missed, thus enabling me to
move forward!
Up until now, I've been embedding Python 2.6.6 in my C++ program, by
compiling with "-I/usr/include/python2.6 -lpython2.6", and all has
been well.
