From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Tom Scogland <scogland1@llnl.gov>
Cc: Farid Zakaria <fmzakari@ucsc.edu>,
guix-devel@gnu.org, Carlos Maltzahn <carlosm@ucsc.edu>
Subject: Re: Alternative solution to stat storm problem
Date: Tue, 18 Jan 2022 15:00:51 +0100 [thread overview]
Message-ID: <87fspli1nw.fsf@gnu.org> (raw)
In-Reply-To: <77415614-71BF-4F54-BBE5-EAFAB10DC31D@llnl.gov> (Tom Scogland's message of "Mon, 10 Jan 2022 10:13:03 -0800")
Hi,
Tom Scogland <scogland1@llnl.gov> skribis:
> You’re right, the LD_LIBRARY_PATH will not change the loading order,
> but using LD_PRELOAD will by the same mechanism we’re using,
> pre-filling the cache with a library at the same soname. As part of
> other explorations we’re doing around tweaking or wrapping the loader,
> it may be possible to get semantics like LD_LIBRARY_PATH other ways,
> but at the moment the goal is to make a program that will correctly
> load all the dependencies it would have loaded were it run in the same
> environment it was built in, despite LD_LIBRARY_PATH or RUNPATH in
> dependencies or similar. Making a little tool that would override the
> same way LD_LIBRARY_PATH would have would be relatively
> straightforward though, would that be worth exploring do you think?
Sure, why not.
My approach was: take the loader and its mechanisms as they exist, and
make the minimal changes needed to adapt it to the
one-directory-per-package layout, when they currently assume FHS.
The approach you describe is more about keeping the loader unchanged and
working around its FHS assumptions “from the outside”. In that spirit,
a separate mechanism for LD_LIBRARY_PATH-kind of user overrides might
make sense.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-01-18 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 20:05 Alternative solution to stat storm problem Farid Zakaria
2022-01-08 21:22 ` Ludovic Courtès
2022-01-09 3:00 ` Farid Zakaria
2022-01-09 3:05 ` Farid Zakaria
2022-01-10 18:13 ` Tom Scogland
2022-01-18 14:00 ` Ludovic Courtès [this message]
2022-01-18 13:56 ` Ludovic Courtès
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=87fspli1nw.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=carlosm@ucsc.edu \
--cc=fmzakari@ucsc.edu \
--cc=guix-devel@gnu.org \
--cc=scogland1@llnl.gov \
/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).