GNU bug report logs - #32995
Executing pre-compiled binaries

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Brett Gilio <brettg <at> posteo.net>
Subject: bug#32995: closed (Re: bug#32995: Executing pre-compiled binaries)
Date: Tue, 09 Oct 2018 14:49:02 +0000

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

Your bug report

#32995: Executing pre-compiled binaries

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 32995 <at> debbugs.gnu.org.

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

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

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Brett Gilio <brettg <at> posteo.net>
Cc: 32995-done <at> debbugs.gnu.org
Subject: Re: bug#32995: Executing pre-compiled binaries
Date: Tue, 09 Oct 2018 15:02:43 +0200

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 <at> oryxpro ~$ cd Downloads/tsetup.1.4.0/Telegram/
>> brettg <at> oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ls
>> Telegram  Updater
>> brettg <at> oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ./Telegram bash:
>> ./Telegram:
>> No such file or directory
>> brettg <at> 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

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

From: Brett Gilio <brettg <at> posteo.net>
To: bug-guix <at> gnu.org  
Subject: Executing pre-compiled binaries
Date: Mon, 08 Oct 2018 23:40:49 -0500

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 <at> oryxpro ~$ cd Downloads/tsetup.1.4.0/Telegram/
brettg <at> oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ls
Telegram  Updater
brettg <at> oryxpro ~/Downloads/tsetup.1.4.0/Telegram$ ./Telegram 
bash: ./Telegram: No such file or directory
brettg <at> oryxpro ~/Downloads/tsetup.1.4.0/Telegram$

Any ideas?


-- 
Brett M. Gilio
Free Software Foundation, Member
https://gnu.org/s/guix/ | https://emacs.org

Previous Next

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