libpython2.7.so.1.0: cannot open shared object file: No such file or directory

Question

I have trying to run python script from the terminal but getting the next error message :

ImportError: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

if I run print sys.version I get :

>>> import sys
>>> print sys.version
2.7.3 (default, Feb 26 2013, 16:27:39)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)]

and if I run ldd /usr/local/bin/python

>> ldd /usr/local/bin/python
        linux-vdso.so.1 =>  (0x00007fff219ff000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003300c00000)
        libdl.so.2 => /lib64/libdl.so.2 (0x0000003300800000)
        libutil.so.1 => /lib64/libutil.so.1 (0x0000003310e00000)
        libm.so.6 => /lib64/libm.so.6 (0x0000003300000000)
        libc.so.6 => /lib64/libc.so.6 (0x0000003300400000)
        /lib64/ld-linux-x86-64.so.2 (0x00000032ffc00000)

I don't understand which python do I have ? why running this python script from the terminal is failing ? I have tried to run

export LD_LIBRARY_PATH=/usr/local/lib/python2.7/

with no luck...

BTW - I have managed to debug this script in eclipse with the python plug-in, and when I look at the debug configuration I see that the PYTHONPATH is set for :

/..../eclipse/plugins/org.python.pydev_3.1.0.201312121632/pysrc/pydev_sitecustomize:/..../workspace/style_checker/src:/usr/local/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg:/usr/local/lib/python2.7/site-packages/pip-1.2.1-py2.7.egg:/usr/local/lib/python2.7:/usr/local/lib/python2.7/plat-linux2:/usr/local/lib/python2.7/lib-tk:/usr/local/lib/python2.7/lib-dynload:/usr/local/lib/python2.7/site-packages

so eclipse manage somehow to find this python2.7 libs... so how can I do it with out eclipse and from the command line ? what am I doing wrong ? using CentOS6.

Have you tried `export LD_LIBRARY_PATH=/usr/local/lib/python2.7/:$LD_LIBRARY_PATH`? In my case, I ran `export LD_LIBRARY_PATH=/home/minh.lengoc/.local/lib:$LD_LIBRARY_PATH` — minhle_r7, Jan 25 '14 at 09:18

CK.Nguyen · Answer 1 · 2018-10-31T01:24:55.327

54

Try to find file libpython2.7.so.1.0:

locate libpython2.7.so.1.0

In my case, it show out put:

/opt/rh/python27/root/usr/lib64/libpython2.7.so.1.0

Then paste line /opt/rh/python27/root/usr/lib64 to file /etc/ld.so.conf

And run ldconfig. It solved my problem. Goodluck!

edited Oct 31 '18 at 01:24

answered Feb 25 '16 at 09:23

CK.Nguyen

1,258
17
16

2

Okay, how to include that? Just pasting the path in the text file? I tried that it did not work. Any other way? – krozaine Jul 30 '16 at 02:15
@ krozaine: Can you paste the output of command `locate libpython2.7.so.1.0` and content of file `/etc/ld.so.conf` ? – CK.Nguyen Aug 01 '16 at 12:39
I'm curious why this isn't handled by the python2.7 rpm installation? It seems like a packaging oversight? – Emmel Feb 10 '17 at 16:15
libpython2.7.so.1.0 does not exist on my system. $ python -V ... 2.7.12 – Kyle Anderson Jan 12 '18 at 19:01
1

-- You can use `whereis libpython2.7.so.1.0` to locate the file. :) – atb00ker Jun 19 '18 at 13:54
@atb00ker `whereis` did not yield any results for me, but `locate` did. – Joshua Schlichting Jun 21 '20 at 22:58

score 31 · Answer 2 · edited Mar 27 '18 at 19:29

31

For some reason these two have worked perfectly for me:

apt-get install libpython2.7
sudo apt-get install libatlas3-base

I found them here and here

edited Mar 27 '18 at 19:29

Paul Roub

36,322
27
84
93

answered Mar 27 '18 at 19:26

John Kitonyo

2,109
1
14
17

6

Just installing libpython2.7 did it – rightaway717 Jun 20 '19 at 11:36
Only "apt-get install libpython2.7" is worked. No needed to install others – Erol Erdogan Jan 10 '22 at 13:28

HelloWorld101 · Answer 3 · 2021-08-02T09:50:07.347

3

For me, the answer at https://stackoverflow.com/a/1100297/3559967 worked. The author of that question also stated that the LD_LIBRARY_PATH approach did not work for him, but adding the library path to /etc/ld.so.conf and running ldconfig worked.

edited Aug 02 '21 at 09:50

answered Oct 28 '14 at 09:52

HelloWorld101

3,878
2
34
47

score 3 · Answer 4 · answered Aug 13 '19 at 12:22

3

I was having a similar issue while executing a 32 bits gdb binary on a 64 bits Linux:

arm-eabi-gdb: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

and I solved it by installing libpython2.7:i386 (note the :i386 suffix)

answered Aug 13 '19 at 12:22

Clément Hurlin

440
3
11

Me too. Work with *Ubuntu 20.04 x86-64 – dceccon Feb 04 '21 at 10:51

score 1 · Answer 5 · answered Sep 10 '18 at 21:16

This isn't a subject I'm keen on, but my understanding is for Linux machines especially (where you're compiling python binaries) that shared library directories should be specified at the compile step.

For instance, following the linked example, here is how I ensure libpython2.7.so.1.0 is included in addition to other libraries:

./configure --enable-shared \
        --prefix=/directory/for/Python-2.7.15 \
        LDFLAGS="-Wl,--rpath=/usr/local/lib -Wl,--rpath=/directory/for/Python-2.7.15"

Notice I'm also installing python to a fixed directory of my choosing, via the --prefix option. That might not be necessary for you, but I did it to provide a solution for the general case where your python install might be located anywhere.

With the above solution, I never have to export LD_LIBRARY_PATH or mess with ldconfig

score 1 · Answer 6 · answered Dec 14 '18 at 09:42

1

I solved it by using "export LD_LIBRARY_PATH="${WORK_PATH}/venv/lib".

answered Dec 14 '18 at 09:42

刘远圳

594
6
5

score 0 · Answer 7 · answered Feb 27 '19 at 16:22

0

Adding to the Correct answer:

Multiple question on how to the following : Then paste line /opt/rh/python27/root/usr/lib64 to file /etc/ld.so.conf

The correct way to do this add a new file in /etc/ld.so.conf.d/, and add the line above in that file.

answered Feb 27 '19 at 16:22

rrpr

95
1
1
6

libpython2.7.so.1.0: cannot open shared object file: No such file or directory

7 Answers7

Linked