libpython not found on Arch Linux with Python 3.9? #2184
-
|
Hi! I purchased Binary Ninja a while ago, and it's been working great so far! But I booted it up today and was greeted with some errors about not being able to find libpython, which I think is related to Arch finally upgrading to Python 3.9 about a week ago. I can see there is a I am on the latest development build by the way, which according to the change log should have support for Python 3.9
EDIT: Starting Binary Ninja with the LD_PRELOAD environment variable ( |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
You need to manually specify the interpreter in settings (search for "interpreter") and point it at the We try to update the list of default locations and names to detect so we can probably add that as well, but this work-around is often required for platforms that we don't officially support such as arch since we don't test them regularly. |
Beta Was this translation helpful? Give feedback.
-
|
Yep that worked, thank you! It did suggest the correct path by the way, so I'm guessing it was indeed in one of the standard locations. Could it be that this setting just isn't automatically updated when the system's Python version is upgraded? Perhaps that is intended behavior, but I thought I'd just let you know :) |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, yes, if you've manually selected a pervious python your settings file is updated but then if a system update changes it, you'll need to update it. If you've never manually set one, it should automatically find an appropriate one. You can see if the setting has been changed based on whether |
Beta Was this translation helpful? Give feedback.
-
|
That's strange, because I'm pretty sure I hadn't manually set a Python version before (otherwise I would've known about the setting and just changed it after updating). Oh well, it's working now ¯\_(ツ)_/¯ |
Beta Was this translation helpful? Give feedback.
You need to manually specify the interpreter in settings (search for "interpreter") and point it at the
.so.We try to update the list of default locations and names to detect so we can probably add that as well, but this work-around is often required for platforms that we don't officially support such as arch since we don't test them regularly.