What I should have clarified:
- This is on Linux
- I am not concerned with the binary not working, but I think the error
message is unclear and misleading.
$ ldd /home/pp/bin/caddy
/home/pp/bin/caddy: error while loading shared libraries:
/usr/lib/x86_64-linux-gnu/libc.so: invalid ELF header
$ strace -e open,stat,execve -f /home/pp/bin/caddy
strace -e open,stat,execve -f /home/pp/bin/caddy
execve("/home/pp/bin/caddy", ["/home/pp/bin/caddy"], [/* 74 vars */]) =
-1 ENOENT (No such file or directory)
strace: exec: No such file or directory
+++ exited with 1 +++
$ file /home/pp/bin/caddy
/home/pp/bin/caddy: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib/amd64/ld.so.1, not stripped
$ /home/pp/bin/caddy
-bash: /home/pp/bin/caddy: No such file or directory
The output from bash is misleading. The file is there. Couldn't the
error message be more descriptive of what's the actual problem?
Peter
On 05/05/2560 20:01, Eduardo Bustamante wrote:
> On Thu, May 4, 2017 at 10:57 PM, Peter Passchier <pe...@passchier.net> wrote:
> [...]
>> $ file /home/pp/bin/caddy
>> /home/pp/bin/caddy: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
>> dynamically linked, interpreter /lib/amd64/ld.so.1, not stripped
>
> (I'm assuming you're trying to run this in a Linux system)
>
> Can you show:
>
> - The output from: ldd /home/pp/bin/caddy
> - The output from: strace e open,stat,execve -f /home/pp/bin/caddy
>
