From: Maxime Devos <maximedevos@telenet.be>
To: Haider Mirza <x7and7@gmail.com>, 54941@debbugs.gnu.org
Subject: bug#54941: No such file or directory when running a binary
Date: Sat, 16 Apr 2022 15:25:24 +0200 [thread overview]
Message-ID: <76dcf44e10f068001079b065518ba8866f149ed3.camel@telenet.be> (raw)
In-Reply-To: <87h76v1xs4.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
Haider Mirza schreef op do 14-04-2022 om 16:34 [+0100]:
> I am trying to run a binary and it returns "bash: ./silent-syphon: No
> such file or directory"
> This issue does not seem to happen on other distros (tested on
> Archlinux) and has been reproduced on several GNU Guix installations.
> This error has occured before and every both times the binary was
> originally found in a zip file. I unzip the file with "unzip foo".
> Using the unzip program.
It probably uses /lib64/ld-linux-x86-64.so.2 or the like which does not
exist on Guix. What is the interpreter according to "readelf -l
silent-python"? (look for ‘Requesting program interpreter: ’ in the
output). What does 'stat THE-INTERPRETER’ say?
> LDD shows the binary to be fine and error continued to happen even
> after installing all dependancies/libraries.
'ldd' is not perfect. As an additional test, could be to do "strace
./silent-python", maybe it tells you which file could not be found.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-16 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 15:34 bug#54941: No such file or directory when running a binary Haider Mirza
2022-04-16 13:25 ` Maxime Devos [this message]
2022-04-16 13:32 ` Maxime Devos
2022-04-16 23:32 ` Bengt Richter
2022-04-20 19:46 ` Haider Mirza
2022-04-23 14:47 ` Maxime Devos
2022-04-16 13:58 ` Haider Mirza
2022-04-16 14:16 ` Maxime Devos
2022-04-16 14:22 ` Haider Mirza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76dcf44e10f068001079b065518ba8866f149ed3.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54941@debbugs.gnu.org \
--cc=x7and7@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).