collect2: library libpython2.6 not found while building extensions (--enable-shared)

All, When I configure python to enable shared libraries, none of the extensions are getting built during the make step due to this error. building 'cStringIO' extension gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -I/u01/home/apli/wm/

Re: Problem building python 2.7 with --enable-shared

dded: gcc [...9 -L/vrmd/python2/lib So linking to python2.7 during make doesn't link to the freshly build library, but to the existing in the system. And at least in my case, where I'm switching from a python installation without --enabled-shared to a new version including --enable

Re: Problem building python 2.7 with --enable-shared

The strange thing is: This only happens when I'm compiling through rpmbuild. Issuing the same commands (configure --enable-shared, make, make install) directly on the shell works fine... -- http://mail.python.org/mailman/listinfo/python-list

Re: Problem building python 2.7 with --enable-shared

On Thursday 16 September 2010, it occurred to Marten Lehmann to exclaim: > Hello, > > I've build python 2.7 successfully by just calling configure, make and > make install. But to use python within PostgreSQL, I need to built > python with --enable-shared. > > I

Problem building python 2.7 with --enable-shared

Hello, I've build python 2.7 successfully by just calling configure, make and make install. But to use python within PostgreSQL, I need to built python with --enable-shared. I tried to do so (configure --enable-shared), but I see these lines several times in the log (but compiling cont

Re: how to build with --enable-shared so that binary knows where libraries are.

d d gmail.com> writes: > I found this: > http://koansys.com/tech/building-python-with-enable-shared-in-non-standard-location > It recommends LDFLAGS="-rpath ", and mentions that you > get a "compiler cannot create executables" error unless you first > creat

how to build with --enable-shared so that binary knows where libraries are.

The following is on Linux. I'd like to build python with ./configure --enable-shared. And install in a non-standard place (an nfs-mounted directory). However, the binary is then not usable, since it can't find the library. I can fix this by defining LD_LIBRARY_PATH, but I don't

Compilation problem of Python2.5.1 on AIX5.2 (with --enable-shared option)

distribution The step I tried to compile python as shared library is to follow README, section "Building a shared libpython", which suggests to add --enable-shared during configuration. My problem is that with --enable-shared, the make step could not complete (the error message shows it trie

enable-shared

How we do if find that python that we are using is compiled with the -- enable-shared option. There is can actually be done using distutils.sysconfig module but this modules is ported only with python- devel but not with standard python install. Is there another way apart from checking the

Re: --enable-shared, how do i set the rpath?

Mark Harrison wrote: > I've built a python with --enable-shared in order to support mod_python, > but now I have to set LD_LIBRARY_PATH to $prefix/lib. > > Worse, it seems mod_python will die on some import statements, > I'm suspecting ones that need to pull in .so&#

Re: --enable-shared, how do i set the rpath?

Mark Harrison schrieb: > I've built a python with --enable-shared in order to support mod_python, Why do you think you have to build with --enable-shared to support mod_python? I'd try to avoid --enable-shared if possible. It has undesirable consequences... > but n

--enable-shared, how do i set the rpath?

I've built a python with --enable-shared in order to support mod_python, but now I have to set LD_LIBRARY_PATH to $prefix/lib. Worse, it seems mod_python will die on some import statements, I'm suspecting ones that need to pull in .so's. Any clues appreciated... Mark. -- Mark

Re: Can't compile with --enable-shared on MacOSX

Lothar Scholz wrote: Maarten Sneep <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... On Mac OS X the shared library functionality is obtained through frameworks. It may detect this by default, but I'm not sure about Not good. I don't want frameworks. I must embedd python into my

Re: Can't compile with --enable-shared on MacOSX

Maarten Sneep <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > On Mac OS X the shared library functionality is obtained through > frameworks. It may detect this by default, but I'm not sure about Not good. I don't want frameworks. I must embedd python into my application. Sett

Re: Can't compile with --enable-shared on MacOSX

In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Lothar Scholz) wrote: > i tried to generate a dynamic library from the official > Python-2.4.0.tgz on MacOSX 10.3 but when i do the > > ./configure --enable-shared ; make ; sudo make install > > It links statically.

Can't compile with --enable-shared on MacOSX

Help, i tried to generate a dynamic library from the official Python-2.4.0.tgz on MacOSX 10.3 but when i do the ./configure --enable-shared ; make ; sudo make install or ./configure --enable-shared=yes ; make ; sudo make install It links statically. It's also strange that i can