When a statically-linked executable returns "no such file or directory" upon execution, it could mean multiple things. Typically, ELFs with missing dependencies result in error messages from the linker containing `cannot open shared object file`, not _only_ `No such file or directory`. What you have looks more like missing ELF loader (e.g. `/lib64/ld-linux-x86-64.so.2` on my system, which is the binary that's supposed to load dynamically linked executables and their `.so` dependencies). This may happen on purely 64-bit systems when trying to run a 32-bit executable wanting a 32-bit loader. What does `readelf -e ./sqlite3 | grep interpreter` show for both executables?