From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: 42558@debbugs.gnu.org
Subject: bug#42558: ‘guix pack -RR’: audit library is dynamically linked
Date: Tue, 28 Jul 2020 14:49:46 +0200 [thread overview]
Message-ID: <87r1svu7md.fsf@gnu.org> (raw)
In-Reply-To: <87tuxtuk9m.fsf@inria.fr> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Mon, 27 Jul 2020 16:04:21 +0200")
Ludovic Courtès <ludovic.courtes@inria.fr> skribis:
> The audit library created by ‘guix pack -RR’, called ‘pack-audit.so’, is
> dynamically-linked. Thus, it cannot be loaded (unless there are working
> libgcc.so and libc.so in the search path?), leading to failures like
> this:
>
> $ GUIX_EXECUTION_ENGINE=performance ./bin/sinfo --version
> ERROR: ld.so: object '/…/lcourtes/tmp/t/gnu/store/0n6nnvzgxyisg0bszb5zqxp2gzdwh7h3-pack-audit.so' cannot be loaded as audit interface: cannot open shared object file; ignored.
> /…/lcourtes/tmp/t/gnu/store/3dhy2f3djmm1h5ix5aa84lrskxzrl6d0-slurm-19.05.3-2/bin//sinfo: error while loading shared libraries: libslurmfull.so: cannot open shared object file: No such file or directory
>
> The root cause is that ‘pack-audit.so’ NEEDs libgcc_s.so, which on this
> machine could not be loaded, and thus resolving the other dependencies
> of the wrapped executable, like ‘libslurmfull.so’ here, fails.
Fixed by commit c6c0d5a22c2ee3d7164dab0129b2e4852a4ae76c.
How could this happen? I think there are two key factors:
1. Most likely I tested v1 of the patch series on “real” non-Guix
machines, but when iterating on v2 (which removed ‘--library-path’
from the ld.so invocation¹) I probably relied on
‘tests/guix-pack-relocatable.sh’, which emulates a machine where
/gnu is empty by mounting a tmpfs on it.
2. There was another bug in ‘exec_with_loader’ whereby it would
symlink its store to that writable /gnu. Thus, the tests would run
as if the store was already available under /gnu/store, thereby
hiding the actual issue. This second bug is fixed by
c088aa2988ef82289c87ebfd6d07d8f1464dd8f0.
AFAICS we’re all fine now.
You’re very welcome to give it a spin on a Guix-less machine! Just do:
guix pack -RR your favorite packages -S /bin=bin
Send the resulting tarball to that machine, and then:
mkdir test
cd test
tar xf /path/to/pack.tar.gz
GUIX_EXECUTION_ENGINE=fakechroot ./bin/your-favorite-command
Ludo’.
¹ https://issues.guix.gnu.org/41189#8
prev parent reply other threads:[~2020-07-28 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 14:04 bug#42558: ‘guix pack -RR’: audit library is dynamically linked Ludovic Courtès
2020-07-28 12:49 ` Ludovic Courtès [this message]
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=87r1svu7md.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=42558@debbugs.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 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).