From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#20039: jack2: Dangling .so references Date: Mon, 09 Mar 2015 23:27:20 +0100 Message-ID: <87siddolh3.fsf@gnu.org> References: <874mpvctyu.fsf@taylan.uni.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58168) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YV69c-0005ee-2o for bug-guix@gnu.org; Mon, 09 Mar 2015 18:28:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YV69a-0005lC-28 for bug-guix@gnu.org; Mon, 09 Mar 2015 18:28:04 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:42416) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YV69Z-0005l8-W0 for bug-guix@gnu.org; Mon, 09 Mar 2015 18:28:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YV69Z-0000AC-NC for bug-guix@gnu.org; Mon, 09 Mar 2015 18:28:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: 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") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: "Taylan Ulrich \"=?UTF-8?Q?Bay=C4=B1rl=C4=B1/Kammer?=\"" Cc: 20039@debbugs.gnu.org taylanbayirli@gmail.com (Taylan Ulrich "Bay=C4=B1rl=C4=B1/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=E2=80=99s a bit daunting ;-)). I think there are two things to do: 1. Identify the reasons why these things aren=E2=80=99t in the RUNPATH: missing -L? ld-wrapper bug (introduced in last =E2=80=98core-updates= =E2=80=99?)? 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=E2=80=99.