* bug#32995: Executing pre-compiled binaries
@ 2018-10-09 4:40 Brett Gilio
2018-10-09 4:51 ` Brett Gilio
0 siblings, 1 reply; 3+ messages in thread
From: Brett Gilio @ 2018-10-09 4:40 UTC (permalink / raw)
To: 32995
Hi all, I am having an issue with trying to execute literally any
pre-compiled binary files. One example is Telegram. Here is what
is
happening.
brettg@oryxpro ~$ cd Downloads/tsetup.1.4.0/Telegram/
brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ls
Telegram Updater
brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ./Telegram
bash: ./Telegram: No such file or directory
brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$
Any ideas?
--
Brett M. Gilio
Free Software Foundation, Member
https://gnu.org/s/guix/ | https://emacs.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#32995: Executing pre-compiled binaries
2018-10-09 4:40 bug#32995: Executing pre-compiled binaries Brett Gilio
@ 2018-10-09 4:51 ` Brett Gilio
2018-10-09 13:02 ` Ricardo Wurmus
0 siblings, 1 reply; 3+ messages in thread
From: Brett Gilio @ 2018-10-09 4:51 UTC (permalink / raw)
To: Brett Gilio; +Cc: 32995
Brett Gilio writes:
> Hi all, I am having an issue with trying to execute literally
> any
> pre-compiled binary files. One example is Telegram. Here is what
> is
> happening.
>
> brettg@oryxpro ~$ cd Downloads/tsetup.1.4.0/Telegram/
> brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ls
> Telegram Updater
> brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ./Telegram
> bash: ./Telegram:
> No such file or directory
> brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$
>
> Any ideas?
Also, in the strings evaluation of the binary I am getting
/lib64/ld-linux-x86-64.so.2
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#32995: Executing pre-compiled binaries
2018-10-09 4:51 ` Brett Gilio
@ 2018-10-09 13:02 ` Ricardo Wurmus
0 siblings, 0 replies; 3+ messages in thread
From: Ricardo Wurmus @ 2018-10-09 13:02 UTC (permalink / raw)
To: Brett Gilio; +Cc: 32995-done
Hi Brett,
> Brett Gilio writes:
>
>> Hi all, I am having an issue with trying to execute literally any
>> pre-compiled binary files. One example is Telegram. Here is what is
>> happening.
>>
>> brettg@oryxpro ~$ cd Downloads/tsetup.1.4.0/Telegram/
>> brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ls
>> Telegram Updater
>> brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ./Telegram bash:
>> ./Telegram:
>> No such file or directory
>> brettg@oryxpro ~/Downloads/tsetup.1.4.0/Telegram$
>>
>> Any ideas?
>
> Also, in the strings evaluation of the binary I am getting
> /lib64/ld-linux-x86-64.so.2
This is the dynamic linker/loader. It is provided by the GNU C library.
The best approach is to avoid this problem and build the programme from
source.
Any other approach is really just a hack. Possible hacks are:
1. symlink the dynamic linker/loader from glibc to the expected
location.
2. use “patchelf” to replace the reference to the linker on an FHS
system with a reference to the linker from our glibc.
This would only be the first step. Binaries built and linked elsewhere
are probably also going to have problems finding libraries. Here you
would have to mess with LD_LIBRARY_PATH to satisfy these requirements.
I suggest not going down this road and packaging the software instead.
Since we don’t support the execution of pre-built binaries on Guix I’m
closing the bug report, but I hope my comments have been helpful in your
case.
--
Ricardo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-10-09 14:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-09 4:40 bug#32995: Executing pre-compiled binaries Brett Gilio
2018-10-09 4:51 ` Brett Gilio
2018-10-09 13:02 ` Ricardo Wurmus
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).