python：加载共享库时出错：libpython3.4m.so.1.0：无法打开共享对象文件：没有这样的文件或目录

Question

I have created a python virtual environment using virtualenv , after activating it, I can see where is Python installed in my shell as following:

(virtualenv-test) bash-4.1$ whereis python
python: /usr/bin/python2.6 /usr/bin/python2.6-config /usr/bin/python
/usr/lib/python2.6 /usr/lib64/python2.6 /usr/X11R6/bin/python2.6
/usr/X11R6/bin/python2.6-config /usr/X11R6/bin/python
/usr/bin/X11/python2.6 /usr/bin/X11/python2.6-config
/usr/bin/X11/python /usr/include/python2.6
/usr/share/man/man1/python.1.gz

Also I can see what python version I'm using:

(virtualenv-test) bash-4.1$ which python
/data/virtualenv-test/bin/python

However, after typing python, I got the following error message:

(virtualenv-test) bash-4.1$ python
python: error while loading shared libraries: libpython3.4m.so.1.0: cannot open shared object file: No such file or directory

What can be the underlying reason?

Answer 1

Try adding the python3.4's lib path to the $LD_LIBRARY_PATH environment variable.

First find out the lib path of python3.4 (depends on how you installed python3.4)

For me it was: /opt/python361/lib , then add it to environment variable like so:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/python361/lib

PS I came across a similar problem while using virtualenv with python3.6 , and I fixed it like so:

• First, append include <lib path of python3.x> to /etc/ld.so.conf (Something like: include /opt/python361/lib or include /usr/local/lib )
• Then, activate the new configuration by running sudo /sbin/ldconfig -v .

Answer 2

Another way is adding LDFLAGS="-Wl,-rpath /usr/local/lib" in configure, for example

./configure --prefix=/usr/local --enable-shared LDFLAGS="-Wl,-rpath /usr/local/lib"

/usr/local/lib is the path where libpython3.*.so files are in

Answer 3

对于 Python 3.6，它被修复了

sudo apt-get install libpython3.6-dev

Answer 4

export LD_LIBRARY_PATH=[your python path to libpython3.4m.so]

libpython3.4m.so is under your python source from which you built it.

Put it in your .bashrc to set it at login automatically.

I can't force virtualenv to 3.4 on my machine but you can see that under lib of your virtualenv there's just a bunch of symlink to your local python installation. I guess libpython3.4m.so is fetch by one of those.

Answer 5

Kudos to above, For python 3.X you can fix this issue with:

sudo apt-get install libpython3.x-dev

No need to any changes to environment path manually.

Answer 6

For me, libpython3.6m.so.1.0 was in the folder where I downloaded Python source ( ~/Python3.6.9 ).

I simply did : sudo cp ~/Python3.6.9/libpython3.6m.so.1.0 /usr/local/lib/python3.6/

and : export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib/python3.6

Answer 7

On python 3.8, I resolved this by deleting the virtualenv directory ( ./venv in my case) and recreating using python's built-in venv module installed of the pip-installed virtualenv . I'm on arch linux and also first did sudo pacman -Syu . Python was originally installed using just sudo pacman -S python .

$ rm -r ./venv
$ python -m venv venv
$ . ./venv/bin/activate
$ python --version
Python 3.8.1

Answer 8

This one worked for me.

cd ~/
vim .bashrc
export LD_LIBRARY_PATH=~/miniconda/envs/python3.6/lib/

Answer 9

我通过安装包来运行它

sudo apt-get install libpython3.x-dev