linux-vdso.so.1 (0x00007ffe697c4000)
libboost_system.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x00007f849d6e0000)
libboost_filesystem.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x00007f849d4c7000)
libboost_program_options.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.62.0 (0x00007f849d248000)
libboost_thread.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.62.0 (0x00007f849d020000)
libboost_chrono.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.62.0 (0x00007f849ce19000)
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f849ca34000)
libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f849c7c8000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f849c335000)
libevent_pthreads-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent_pthreads-2.0.so.5 (0x00007f849c132000)
libevent-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 (0x00007f849beea000)
libzmq.so.5 => /usr/lib/x86_64-linux-gnu/libzmq.so.5 (0x00007f849bc60000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f849b8de000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f849b5da000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f849b3c3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f849b1a6000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f849ae07000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f849abff000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f849a9fb000)
libevent_core-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent_core-2.0.so.5 (0x00007f849a7cf000)
libsodium.so.18 => /usr/lib/x86_64-linux-gnu/libsodium.so.18 (0x00007f849a569000)
libpgm-5.2.so.0 => /usr/lib/x86_64-linux-gnu/libpgm-5.2.so.0 (0x00007f849a31c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f849e0ca000)
You need to make sure that they're all the same version as the machine you built it on. If they're different distros, it's probably just easier to build it again on the VPS.
sudo mv xxxcoind/usr/bin/
if you use this way, you can use xxxcoind in any field.
I did not even know that. So any executable that is under /usr/bin will be available systemwide without needing to write the complete path?
Been a longtime user of debian and i thought that this needs some kind of alias to achieve.
Edit: There should be a space between coind executable and /usr/bin path.
It can be anywhere on your $PATH. Try "echo $PATH" in your shell and have a look at all the places it looks for executables. You can append other directories to $PATH and it will search in those too (you can even add . if you're feeling silly).
/home/matt/.opam/4.06.1/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
So if I put xxxcoind in any of those directories, I'll be able to run it without typing out the full path.