GNU bug report logs - #54941
No such file or directory when running a binary

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Haider Mirza <x7and7 <at> gmail.com>
Subject: bug#54941: closed (Re: bug#54941: No such file or directory when
 running a binary)
Date: Sat, 16 Apr 2022 14:17:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#54941: No such file or directory when running a binary

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 54941 <at> debbugs.gnu.org.

-- 
54941: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=54941
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Maxime Devos <maximedevos <at> telenet.be>
To: Haider Mirza <x7and7 <at> gmail.com>, 54941-done <at> debbugs.gnu.org
Subject: Re: bug#54941: No such file or directory when running a binary
Date: Sat, 16 Apr 2022 16:16:06 +0200

[Message part 3 (text/plain, inline)]

Haider Mirza schreef op za 16-04-2022 om 14:58 [+0100]:
> You're right about the fact that the binary is requesting "/lib64/ld-
> linux-x86-64.so.2" Is it possible to force the binary to use another
> interpreter? If not you can close this down.

Yes, here's how to do it on Debian:

$ ~/.guix-profile/lib/ld-linux-x86-64.so.2 /bin/ls
/bin/ls: error while loading shared libraries: libselinux.so.1: cannot
open shared object file: No such file or directory
[failed!]

Though as can be seen above, not all combinations of interpreters and
binaries actually function ...

Greetings,
Maxime.

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: Haider Mirza <x7and7 <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: No such file or directory when running a binary
Date: Thu, 14 Apr 2022 16:34:13 +0100

[Message part 6 (text/plain, inline)]

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.

Easiest way to reproduce this by unzipping the binary in this 
Github repo:
https://github.com/FluxHarmonic/ld50-silent-syphon/releases/tag/dev

The internet suggests that this might be because I am running a 
32-bit program on a 64-bit system.
LDD shows the binary to be fine and error continued to happen even 
after installing all dependancies/libraries.
I am on the Guix Operating system with everything being 
up-to-date.

Can you suggest any sort of fix?

[Message part 7 (text/html, inline)]

[Message part 8 (text/plain, inline)]

-- 
Haider Mirza via Emacs on a GNU/Linux system

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.