all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: woshilapin <woshilapin@tuziwo.info>
To: Marius <mariusgr@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: How to: How to wrap executablea?
Date: Thu, 21 Nov 2024 11:31:33 +0000	[thread overview]
Message-ID: <yBv4IGSfah4Kd08ez6gECLTyOC2rmZLZueOhx1b-c6qhErZu7FK6nx6B2jWm3pkTwL3cKpO0cTM-CtYBl3-XlyrxW_hJWsFxUL9JLXgZqq8=@tuziwo.info> (raw)
In-Reply-To: <9D8BC476-2680-474E-A5C0-1708487C905E@disroot.org>

Hi Marius,
 
> I'm trying to execute a pre compiled program (on a Guix System) that I think is trying to call /lib64/ld-linux-x86-64.so.2 by its absolute path. Since Guix System does use the store and usually makes use of variables like "SHELL", "LIBRARY_PATH", etc. How do I wrap executables that technically are gnu-linux cross platform but use absolute paths that depend on distribution?

It might not be exactly the same problem, but I remember getting around this kind of problem by providing guix's version of the library with `LD_LIBRARY_PATH`. Doing something like this.

```
eval "$(guix shell --search-paths)"
export LD_LIBRARY_PATH="${LIBRARY_PATH}"
```

It's probably a horrible hack (I honestly don't know enough to know if it's nice or horrible), but it got me something to work with.

Hope this helps, and I'd be happy to know of a cleaner solution.

Sincerely,
--
woshilapin / Jean


  reply	other threads:[~2024-11-21 13:12 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 [this message]
2024-11-21 13:31   ` Marius via
2024-11-21 12:00 ` Dev@icepic
2024-11-21 12:26   ` Andreas Enge

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='yBv4IGSfah4Kd08ez6gECLTyOC2rmZLZueOhx1b-c6qhErZu7FK6nx6B2jWm3pkTwL3cKpO0cTM-CtYBl3-XlyrxW_hJWsFxUL9JLXgZqq8=@tuziwo.info' \
    --to=woshilapin@tuziwo.info \
    --cc=help-guix@gnu.org \
    --cc=mariusgr@disroot.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.