[debbugs-tracker] bug#32995: closed (Executing pre-compiled binaries)

[GNU bug Tracking System]

Your message dated Tue, 09 Oct 2018 15:02:43 +0200
with message-id <address@hidden>
and subject line Re: bug#32995: Executing pre-compiled binaries
has caused the debbugs.gnu.org bug report #32995,
regarding Executing pre-compiled binaries
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
32995: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32995
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Executing pre-compiled binaries
>
>
>
>
> Date: 
>
> Mon, 08 Oct 2018 23:40:49 -0500
>
>
>
>
> User-agent: 
>
> mu4e 1.0; emacs 26.1
>
>
>
>
> 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.
>
> address@hidden ~$ cd Downloads/tsetup.1.4.0/Telegram/
> address@hidden ~/Downloads/tsetup.1.4.0/Telegram$ ls
> Telegram  Updater
> address@hidden ~/Downloads/tsetup.1.4.0/Telegram$ ./Telegram 
> bash: ./Telegram: No such file or directory
> address@hidden ~/Downloads/tsetup.1.4.0/Telegram$
>
> Any ideas?
>
>
> --
> Brett M. Gilio
> Free Software Foundation, Member
> https://gnu.org/s/guix/ | https://emacs.org
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#32995: Executing pre-compiled binaries
>
>
>
>
> Date: 
>
> Tue, 09 Oct 2018 15:02:43 +0200
>
>
>
>
> User-agent: 
>
> mu4e 1.0; emacs 26.1
>
>
>
>
> 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.
> >>
> >> address@hidden ~$ cd Downloads/tsetup.1.4.0/Telegram/
> >> address@hidden ~/Downloads/tsetup.1.4.0/Telegram$ ls
> >> Telegram  Updater
> >> address@hidden ~/Downloads/tsetup.1.4.0/Telegram$ ./Telegram bash:
> >> ./Telegram:
> >> No such file or directory
> >> address@hidden ~/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
>
>
>
> --- End Message ---