From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Apoorv via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: Apoorv <apoorvs@tuta.io>
Subject: Re: Suggestion for a guix shell feature.
Date: Thu, 28 Dec 2023 22:58:27 -0500 [thread overview]
Message-ID: <87le9dvevw.fsf@gmail.com> (raw)
In-Reply-To: <Nm8kDp1--3-9@tuta.io> (Apoorv via's message of "Thu, 21 Dec 2023 17:10:56 +0100 (CET)")
Hi,
Apoorv via "Development of GNU Guix and the GNU System distribution."
<guix-devel@gnu.org> writes:
> I want to make a suggestion for a feature for guix shell.
>
> I was recently writing guix.scm files for my projects and was having
> problem with the libraries I added, not being found inside the
> shell. After struggling for hours I finally learned that that the
> LD_LIBRARY_PATH is not being updated automatically inside the guix
> shell environment so the libraries can be found easily.
>
> So my feature suggestion is that maybe we can have a flag or a option
> for guix shell, something like --add-ld-path or --update-ld-path for
> example, to add all libraries specified in the guix.scm or even as
> sub-command guix shell --add-ld-path mesa as an example, to
> automatically update the LD_LIBRARY_PATH environment variable to
> contain the correct paths to these libraries so they can be found
> easily inside the shell.
Guix doesn't/shouldn't make use of LD_LIBRARY_PATH, except in rare cases
to wrap binaries. It's better to patch the dlopen calls to use the
absolute shared library file name.
Perhaps you are missing the package configuring LIBRARY_PATH and other
useful environment variables for finding libraries? That'd be
gcc-toolchain, if I recall correctly.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-12-29 3:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 16:10 Suggestion for a guix shell feature Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-29 3:58 ` Maxim Cournoyer [this message]
2023-12-29 13:50 ` Ekaitz Zarraga
2023-12-29 15:39 ` Tobias Geerinckx-Rice
2023-12-29 17:21 ` Maxim Cournoyer
[not found] <NmrVHaU--3-9@tuta.io>
2023-12-30 3:10 ` Maxim Cournoyer
2023-12-31 12:10 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-31 16:55 ` Maxim Cournoyer
2024-01-01 3:01 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2024-01-02 16:33 ` Maxim Cournoyer
2024-01-03 9:14 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2024-01-03 17:57 ` Maxim Cournoyer
2024-01-05 13:38 ` Apoorv via Development of GNU Guix and the GNU System distribution.
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=87le9dvevw.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=apoorvs@tuta.io \
--cc=guix-devel@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.
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.