unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Farid Zakaria <fmzakari@ucsc.edu>
Cc: guix-devel@gnu.org, "Scogland, Tom" <scogland1@llnl.gov>,
	Carlos Maltzahn <carlosm@ucsc.edu>
Subject: Re: Alternative solution to stat storm problem
Date: Sat, 08 Jan 2022 22:22:15 +0100	[thread overview]
Message-ID: <878rvp53eg.fsf@gnu.org> (raw)
In-Reply-To: <CAH4OOv6uQhiYWo-0QGD=odAAZv-Kva-xY5_ykbC5PMw+03DchQ@mail.gmail.com> (Farid Zakaria's message of "Mon, 3 Jan 2022 12:05:51 -0800")

Hi Farid,

Farid Zakaria <fmzakari@ucsc.edu> skribis:

> I have written a tool _shrinkwrap_ [2] that takes all transitive
> dynamic shared object dependencies (only those listed in DT_NEEDED)
> and turns them into an absolute path.
>
> This has the same result as caching the entries and avoids the
> unnecessary failed attempts at trying each RUNPATH entry.
>
> Using the same demo application _emacs_ shows as much as well:

Nice!  I think that’s another interesting way to address the problem.

I guess the advantage is that you don’t need the ld.so patch.  The
downside is that PatchELF needs to be able to write longer NEEDED
strings in the dynamic section, which it may not always be successful at
(I think?).

Also, I wonder if the absolute file names in NEEDED interfere with uses
of $LD_LIBRARY_PATH (making it impossible to force use of another
libxyz.so than the one that would be found in RUNPATH.)

Thoughts?

Thanks for sharing!

Ludo’.


  reply	other threads:[~2022-01-08 21:23 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 [this message]
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
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=878rvp53eg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).