From: "Léo Le Bouter via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 47228@debbugs.gnu.org
Subject: bug#47228: Check binary consistency after grafting with e.g. ldd
Date: Thu, 18 Mar 2021 11:37:01 +0100 [thread overview]
Message-ID: <22d6fde28a4646254061f56c342fb75d2a2846d9.camel@zaclys.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
Hello!
We had an issue after grafting ImageMagick fixed by <
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=2e0ff59f0cd836b156f1ef2e78791d864ce3cfcd
>.
Basically Inkscape did not work because ImageMagick's soname had been
bumped (probably for forward compat?):
/gnu/store/g75q5v1gqi4x08qcf1ydfl9xhp4slmxy-inkscape-
1.0.2/bin/.inkscape-real: error while loading shared libraries:
libMagickCore-6.Q16.so.6: cannot open shared object file: No such file
or directory
It seems technically possible to automatically check for this kind of
breakage, therefore I suggest we run ldd (might actually run code from
the binary) or objdump -x (pure static analysis), so after grafting we
could check that every binary can load all it's dependents declared in
the ELF headers successfully and report errors if not?
What do you think?
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-03-18 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 10:37 Léo Le Bouter via Bug reports for GNU Guix [this message]
2021-03-18 13:38 ` bug#47228: Check binary consistency after grafting with e.g. ldd Ludovic Courtès
2021-03-19 8:58 ` Léo Le Bouter via Bug reports for GNU Guix
2021-03-19 10:39 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22d6fde28a4646254061f56c342fb75d2a2846d9.camel@zaclys.net \
--to=bug-guix@gnu.org \
--cc=47228@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
/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.