You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is also an earlier stament: You can also use the static binary that provides support for all compression levels and does not require the libraries to be installed on your system.
All the links igo to from this page lead to https://github.com/fdupoux/fsarchiver/releases where there are no static binaries, I have download tar.gz and taken fsarchiver from it and any attempt to execute gives messages susc as:
./fsarchiver: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory
file fsarchiver
fsarchiver: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=c9f5e770c09cef5379eb6af2f6b9d1e044137369, stripped
So it is dynamiclly linked not static.
Wher is there a static binary that can be used with rescue systems that cannot use the dynamic version.
The text was updated successfully, but these errors were encountered:
https://www.fsarchiver.org/installation/ says there is a static binary, section Installation of the precompiled binary says
There is also an earlier stament: You can also use the static binary that provides support for all compression levels and does not require the libraries to be installed on your system.
All the links igo to from this page lead to https://github.com/fdupoux/fsarchiver/releases where there are no static binaries, I have download tar.gz and taken fsarchiver from it and any attempt to execute gives messages susc as:
./fsarchiver: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory
file fsarchiver
fsarchiver: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=c9f5e770c09cef5379eb6af2f6b9d1e044137369, stripped
So it is dynamiclly linked not static.
Wher is there a static binary that can be used with rescue systems that cannot use the dynamic version.
The text was updated successfully, but these errors were encountered: