From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: bug#22659: Collision of /bin/ld Date: Wed, 17 Feb 2016 17:35:48 +0000 Message-ID: References: <20160214091227.GA10462@jasmine> <87twl9pbas.fsf@netris.org> <20160216195923.GB19703@jasmine> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0111dfcac71db1052bfaae45 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43646) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aW62E-0008OY-2S for bug-guix@gnu.org; Wed, 17 Feb 2016 12:37:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aW62A-0007ul-Pe for bug-guix@gnu.org; Wed, 17 Feb 2016 12:37:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:34486) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aW62A-0007uh-MD for bug-guix@gnu.org; Wed, 17 Feb 2016 12:37:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aW62A-0001fj-GL for bug-guix@gnu.org; Wed, 17 Feb 2016 12:37:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20160216195923.GB19703@jasmine> 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: 22659@debbugs.gnu.org, leo@famulari.name, Mark H Weaver Cc: 22659-done@debbugs.gnu.org --089e0111dfcac71db1052bfaae45 Content-Type: text/plain; charset=UTF-8 > This collision is expected. The 'ld' within ld-wrapper, generated from > the template in gnu/packages/ld-wrapper.in, automatically adds -rpath > arguments to the linker for each shared library, so that the runtime > linker will be able to find them in their non-standard locations. If one of those 'ld' files is the real ld, and the other is supposed to be a wrapper around the real one that adds functionality, then how is it that things will always work out OK if only one of them is installed? I'm not sure how the "arbitrary" selection works, but doesn't the choice matter? --089e0111dfcac71db1052bfaae45 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > This collision is expected. The 'ld' within ld-wrapper, gener= ated from
> the template in gnu/packages/ld-wrapper.in, automatically adds -rpath
> arguments to the = linker for each shared library, so that the runtime
> linker will be = able to find them in their non-standard locations.

If on= e of those 'ld' files is the real ld, and the other is supposed to = be a wrapper around the real one that adds functionality, then how is it th= at things will always work out OK if only one of them is installed? I'm= not sure how the "arbitrary" selection works, but doesn't th= e choice matter?
--089e0111dfcac71db1052bfaae45--