unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org,  Apoorv <apoorvs@tuta.io>
Subject: Re: Suggestion for a guix shell feature.
Date: Fri, 29 Dec 2023 12:21:31 -0500	[thread overview]
Message-ID: <87cyuovs9w.fsf@gmail.com> (raw)
In-Reply-To: <0BD1014A-4C56-48CF-AE38-E06107AFB42F@tobias.gr> (Tobias Geerinckx-Rice's message of "Fri, 29 Dec 2023 15:39:09 +0000")

Hi,

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Hiyall,
>
> On 29 December 2023 03:58:27 UTC, Maxim Cournoyer
> <maxim.cournoyer@gmail.com> wrote:
>>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.
>
> Fully agree.
>
> Furthermore, '--ld-library-path' sounds like an inflexible alias of a
> nonexistent '--ad-hoc-search-path=FOO=/bar' option.
>
> So why not instead write a cute little (name "LD_LIBRARY_PATH") fake
> package that does nothing but declare a search path for /lib?  It
> could live in any channel rather than further fatten 'guix shell'.
>
>>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.
>
> I might be mistaken but I assumed this was more about running
> 'pre-existing' (cough cough nudge nudge) software not built from
> source.

Ah, if this is the case, the 'guix shell --container --emulate-fhs' may
help, by providing some FHS layout with libraries under e.g. /usr/lib/.

-- 
Thanks,
Maxim


  reply	other threads:[~2023-12-29 17:22 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
2023-12-29 13:50   ` Ekaitz Zarraga
2023-12-29 15:39   ` Tobias Geerinckx-Rice
2023-12-29 17:21     ` Maxim Cournoyer [this message]
     [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

  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=87cyuovs9w.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=apoorvs@tuta.io \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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 public inbox

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

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).