This is a two pronged question... The context of the question is getting a good Python 3.1.1 build to use with building and running mod_wsgi. See this document for more information on why a shared library is a good idea.
What are the ramifications of building Python with --enable-shared?
I observe that when I build it WITHOUT --enable-shared, the python binary is ~ 16MB
-rwxr-xr-x 2 root root 1638104 Aug 17 12:29 python3.1
With --enable-shared, the python binary is 15K.
-rwxr-xr-x 2 root root 15860 Oct 5 22:34 python3.1
In general, what does that do to "normal" operations of python? Will all scripts still run the same? Any performance impact? Can you, or is it desirable, to have both (shared and static)?
Any ideas on how to solve this error cleanly?
Note: built on a clean RHEL 5.3 64 bit install.
After building Python 3.1.1 with
./configure --enable-shared, I get this error:
[root@test ~]# python3 python3: error while loading shared libraries: libpython3.1.so.1.0: cannot open shared object file: No such file or directory
I solved it by placing this symlink:
/usr/lib64/libpython3.1.so.1.0 -> /usr/local/lib/libpython3.1.so.1.0
Which seems quite hackish... Are there ./configure options that can be passed to cure this?