question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to open lib libpython3.4.so

See original GitHub issue

Hi,

I’ve just installed cocotb (11th May) on a ubuntu machine and I’m having trouble running the example testcase e.g. endian_swapper with Icarus (0.9.7). Im using v3.4 of python, make v3.81. Do I need to declare some additional environment variable with python v3.4? An earlier cocotb was working when I had python 2.7

Here is the error from the make command

vvp -M /home/damian/Projects/Work/NXP/cocotb/build/libs/i686 -m gpivpi sim_build/sim.vvp
Unable to open lib libpython3.4.so (libpython3.4.so: cannot open shared object file: No such file or directory) Failed to find python lib -.–ns INFO cocotb.gpi GpiCommon.cpp:47 in >gpi_print_registered_impl VPI registered Traceback (most recent call last): File “/home/damian/Projects/Work/NXP/cocotb/cocotb/init.py”, line 41, in <module> import cocotb.handle File “/home/damian/Projects/Work/NXP/cocotb/cocotb/handle.py”, line 46, in <module> import simulator ImportError: /home/damian/Projects/Work/NXP/cocotb/build/libs/i686/simulator.so: undefined symbol: PyModule_GetState Failed to load “cocotb”

Great project any help appreciated.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:15 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
damnsavagecommented, May 16, 2015

That’s it. I see from your link that you have the same warning but like you said it’s not the source of the problem. The python-config I had was v2.7 and my python is v3.4, I fixed this by adding this link

     ln -s /home/damian/anaconda3/bin/python3.4m-config /home/damian/anaconda3/bin/python-config

The endian swapper works now. Thanks for your help 😃

0reactions
stuarthodgsoncommented, Apr 1, 2016

This potential issue will have been resolved by the recent changes in #419

Read more comments on GitHub >

github_iconTop Results From Across the Web

python: error while loading shared libraries: libpython3.4m.so ...
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 ...
Read more >
python: error while loading shared libraries - Archeaopteryx
python manage.py runserver python: error while loading shared libraries: libpython3.7m.so.1.0: cannot open shared object file: No such file or directory.
Read more >
python - How to Resolve "error while loading shared libraries ...
How to Resolve "error while loading shared libraries: libpython3.7m.so.1.0: cannot open shared object file: No such file or directory" on Ubuntu ...
Read more >
Error While Loading Shared Libraries: libpython3.4m.so.1.0
python3: error while loading shared libraries: libpython3.4m.so.1.0: cannot open shared object file: No such file or directory Solution: ...
Read more >
Issue 38987: 3.8.0 on GNU/Linux fails to find shared library
For more information, see the GitHub FAQs in the Python's ... while loading shared libraries: libpython3.8.so.1.0: cannot open shared object ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found