will show, which libraries do your binary want to link in. You will see, exactly which ones can't be found.
You can check the architecture of a shared lib with the command
file -szL /lib/libsomething.so.a.b.c
It will say, if it is an i386 or an amd64 library. The same is for your
The architectures should match. Although the
ldd already shows, what exactly exists and what isn't.
Most distributions have at least a limited multi-arch support, what means, your system can have libraries and binaries coincidentally for multiple architectures.
Find the packages containing the missing libraries (on rpm-based distributions, it can be done with the
scout tool, or deb-based ones with
apt-file). Install them (on rpm, with
yum, on debian,
If the given libraries don't exist on your distribution, then you have to get them from an external source. However, manipulating the system libraries because a single binary is not useful.
Mostly, these libraries exist on a different version of the same distribution (on debian, you can find it on http://packages.debian.org, for other distros I don't know). Download the packages, extract them manually (on rpm, the command is:
rpm2cpio something.rpm|cpio -i -d, on debian:
dpkg -x something.deb; tar -Jxvf data.tar.xz), copy the required library files into the given directory.
With prefixing a binary by
you can start
XCOM2 by giving this additional directory to the shared lib search path.