From: Ricardo Wurmus <rekado@elephly.net>
To: Brett Gilio <brettg@posteo.net>
Cc: 32995-done@debbugs.gnu.org
Subject: bug#32995: Executing pre-compiled binaries
Date: Tue, 09 Oct 2018 15:02:43 +0200 [thread overview]
Message-ID: <874ldvqnm4.fsf@elephly.net> (raw)
In-Reply-To: <87pnwj67th.fsf@posteo.net>
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
prev parent reply other threads:[~2018-10-09 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=874ldvqnm4.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=32995-done@debbugs.gnu.org \
--cc=brettg@posteo.net \
/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).