By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,369 Members | 1,138 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,369 IT Pros & Developers. It's quick & easy.

built with --enable-shared but get error: libpython2.3.so.1.0: can't open shared object file

P: n/a
Hi,

Please release me from my own private hell.

Platform: SuSE 8.1

I'm installing python 2.3 tarball as follows:

../configure --enable-shared
make
make install

When I simply type:

% python

I get:

python: error while loading shared libraries: libpython2.3.so.1.0:
cannot open shared object file: No such file or directory

This is really, really, frustrating. The file does in fact live in
/usr/local/lib. Interestingly this is outside PYTHONHOME. How do I fix
this silly problem (which the python install process should *never*
let happen in the first place).
-Doug
Jul 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
tu****@mmedia.is (Douglass Turner) writes:
Please release me from my own private hell.
OK, just install the non-shared library build.
Platform: SuSE 8.1

I'm installing python 2.3 tarball as follows:

./configure --enable-shared
make
make install

When I simply type:

% python

I get:

python: error while loading shared libraries: libpython2.3.so.1.0:
cannot open shared object file: No such file or directory

This is really, really, frustrating. The file does in fact live in
/usr/local/lib.
Is that in /etc/ld.so.conf? Maybe you should set LD_LIBRARY_RUN_PATH
(or whatever it's called).
Interestingly this is outside PYTHONHOME. How do I fix this silly
problem (which the python install process should *never* let happen
in the first place).


Unclear what Python can do. If you want to install a shared library
somewhere that the system doesn't look for it by default, you have to
do something to get it to look there. I guess there's probably some
way of putting an absolute path in the executable, but that leads to
its own form of entertainment (like, I would imagine, not being able
to run the interpreter until you install it).

Cheers,
mwh

--
It could be argued that since Suitespot is infinitely terrible,
that anything else, by very definition of being anything else,
is infinitely superior. -- ".", alt.sysadmin.recovery
Jul 18 '05 #2

P: n/a
tu****@mmedia.is (Douglass Turner) writes:
python: error while loading shared libraries: libpython2.3.so.1.0:
cannot open shared object file: No such file or directory

This is really, really, frustrating. The file does in fact live in
/usr/local/lib. ...


Try running

/sbin/ldconfig -v | less

it should list libpython2.3.so.1.0 and starting python should now
automagically load the shared library.

--
Manfred
Jul 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.