Completely off topic but thank you ! I was starting C programming and I was wondering how to check an executable dependencies. If I were to package an executable which was dynamically linked to use it on another computer without recompiling binaries, how could I proceed ? does ldd show the dependencies of the dependencies too ? Would it be sufficient to put all shared libraries into the same folder as the executable ? thanks.
Even better, one can embed the relative path to dynamic libraries by editing the RPATH or RUNPATH attributes in the binary (and using $ORIGIN in the path). Check out chrpath and patchelf.
> static linked on a kde library that had widget, new one doesn't have that nor a fallback, application crashes.
As I said before, please read up on what static linking means.
> like, mindrover the europa project port.
...version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2... Clearly not a statically linked binary.