You are not logged in.
Pages: 1
Topic closed
When I started the service libvirtd.service, and I got the error message:
"systemctl: error while loading shared libraries: libffi.so.7: cannot open shared object file: No such file or directory"
I had install the libffi on the system:
[root@archlinux lib]# pacman -Ss libffi
core/libffi 3.4.2-4 [installed]
Portable foreign function interface library
community/haskell-libffi 0.1-26
A binding to libffi
But I found the version libffi is libffi.so.8 not libffi.so.7:
[root@archlinux lib]# pacman -Si libffi
Repository : core
Name : libffi
Version : 3.4.2-4
Description : Portable foreign function interface library
Architecture : x86_64
URL : https://sourceware.org/libffi/
Licenses : MIT
Groups : None
Provides : libffi.so=8-64
Depends On : glibc
Optional Deps : None
Conflicts With : None
Replaces : None
Download Size : 44.90 KiB
Installed Size : 94.37 KiB
Packager : Evangelos Foutras <foutrelis@archlinux.org>
Build Date : Sat Oct 16 10:52:04 2021
Validated By : MD5 Sum SHA-256 Sum Signature
So how could I install the version from libffi.so.8 to libffi.so.7 ?
Last edited by alvinshih (2021-10-22 09:08:52)
Offline
So how could I install the version from libffi.so.8 to libffi.so.7 ?
You don't need to do that, you need to fix your system to work with libffi.so.8. Start by making sure your system is fully updated
Offline
Thanks you. Great help for me.
I run the Pacman -Syu, and fix this problem.
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
OK, I'll mark it.
Offline
I would add that updating the system didn't solve the issue for me. The simplest dumb solution was to force install of the `libffi7` package alongside `libffi8` after update.
Offline
If this didn't work for you then it means you have a core library on your system that is not from the Arch repos, or an old version being resolved due to local overrides, which is an issue you should fix properly instead of relying on old library crutches. However you should open a new thread if you actually want to look at this.
Offline
The issue came after upgrading the system and python 3.7. this broke my virtualenvs. Since installing the dedicated library solved the issue, I can't tell you exactly what happened. I use only Arch repos for updates.
Offline
You need to rebuild your python3.7 against the new lib and update the references to it in your venv if you didn't use symlinks.
In any case, please open a new topic should you want further help with this.
Closing here.
Offline
Pages: 1
Topic closed