From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: 20039@debbugs.gnu.org
Subject: bug#20039: jack2: Dangling .so references
Date: Mon, 09 Mar 2015 23:27:20 +0100 [thread overview]
Message-ID: <87siddolh3.fsf@gnu.org> (raw)
In-Reply-To: <874mpvctyu.fsf@taylan.uni.cx> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Sun, 08 Mar 2015 17:52:25 +0100")
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> While looking into another issue, I happened to notice dangling .so
> references in some executables in Guix packages. This is the first in a
> series of bug reports for each such package. Some might be false
> positives; Mark suggested I report them all so we have a list to go
> through. It's also not comprehensive because of course I don't have
> every Guix package installed; the script to go through one's /gnu/store
> to get output such as the following for each package is attached at the
> bottom of this mail.
Nice, thanks the reports (although it’s a bit daunting ;-)).
I think there are two things to do:
1. Identify the reasons why these things aren’t in the RUNPATH:
missing -L? ld-wrapper bug (introduced in last ‘core-updates’?)?
2. Add a standard phase in gnu-build-system.scm, based on (guix elf),
that checks whether things in DT_NEEDED can actually be found among
the directories in DT_RUNPATH, and errors out if not.
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-03-09 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 16:52 bug#20039: jack2: Dangling .so references Taylan Ulrich Bayırlı/Kammer
2015-03-09 22:27 ` Ludovic Courtès [this message]
2015-03-30 16:06 ` bug#20039: Generic RUNPATH sanity checking Ludovic Courtès
2015-05-07 20:18 ` bug#20039: jack2: Dangling .so references 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=87siddolh3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=20039@debbugs.gnu.org \
--cc=taylanbayirli@gmail.com \
/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.