Open mattogrady87 opened 5 years ago
Because the linux build is for ubuntu and its latest version of libpcap is 0.8.
You can compile it yourself easily so that you don't need to symlink the file.
I want to say that this is also a problem on fedora. On the other hand, raspbian only ships 0.8, so I can understand this decision.
EDIT: In raspbian libpcap.so.0.8 is a symlink to libpcap.so.1.8.
Could you name the binaries such that it's implied they're Ubuntu-only then? At a glance, the -linux suffix would imply it's some binary that works on multiple distributions (e.g. a statically linked one, or with non-libc dependencies statically linked).
Note that fedora and arch use version 1.9 while raspbian (probably debian and ubuntu too) 1.8, fedora names it libpcap.so.1 but raspbian calls it 0.8.
Could lan-play
use whichever is present? It seems both versions are ABI compatible.
Flatpak or docker image would be good!
Why you have to use an ancient version of libpcap0.8 when its now at 1.9? I want to use this software on my Arch dist but I don't want to downgrade my libpcap and break other stuff :(
Edit:
Incase anyone else has this issue, all I did was create a symlink like this:
Assuming that your libpcap is called libpcap.so and in your
/usr/lib/
directory.