From: Andreas Enge <andreas@enge.fr>
To: "Dev@icepic" <dev@icepic.de>
Cc: help-guix@gnu.org
Subject: Re: How to: How to wrap executablea?
Date: Thu, 21 Nov 2024 13:26:40 +0100 [thread overview]
Message-ID: <Zz8nAGgOblIaKt59@jurong> (raw)
In-Reply-To: <D346FDBB-F99F-495D-9C37-784FDA12BE09@icepic.de>
Am Thu, Nov 21, 2024 at 01:00:54PM +0100 schrieb Dev@icepic:
> I think you need to rewrite the path to the dependencies of the executable using `patchelf`, so that the libs from the store are used. I only have done this in nix, but it should be the same for guix? Maybe someone with more experience can comment on this.
I think you need to use "patchelf --set-interpreter FILENAME" for the
ld-linux.so bit. I have done it in the past, but try to avoid it, as in the
end running prebuilt binaries is always a hit-or-miss experience, possibly
after spending quite some time trying to make things work.
Andreas
prev parent reply other threads:[~2024-11-21 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 18:24 How to: How to wrap executablea? Marius via
2024-11-21 11:31 ` woshilapin
2024-11-21 13:31 ` Marius via
2024-11-21 12:00 ` Dev@icepic
2024-11-21 12:26 ` Andreas Enge [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=Zz8nAGgOblIaKt59@jurong \
--to=andreas@enge.fr \
--cc=dev@icepic.de \
--cc=help-guix@gnu.org \
/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.
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).