GNU bug report logs - #22659
Collision of /bin/ld

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22659 in the body.
You can then email your comments to 22659 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: Collision of /bin/ld
Date: Sun, 14 Feb 2016 04:12:27 -0500

Invoking `guix environment guix`, I found this collision alarming. Do
you think it's a problem?

I ran `guix pull` yesterday or the day before. Is there a way to
determine the git commit that corresponds with this version of Guix?

I added the line breaks.

warning: collision encountered:
/gnu/store/agnxzx1yza8ci0a1gz5pds8gdg8qmnz5-ld-wrapper-0/bin/ld
/gnu/store/dki0v5cvf1mhfz571k622xvzi1nyinl2-binutils-2.25.1/bin/ld 

warning: arbitrarily choosing
/gnu/store/agnxzx1yza8ci0a1gz5pds8gdg8qmnz5-ld-wrapper-0/bin/ld

Message #8 received at 22659 <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: 22659 <at> debbugs.gnu.org
Subject: Re: bug#22659: Collision of /bin/ld
Date: Mon, 15 Feb 2016 22:46:19 -0500

Leo Famulari <leo <at> famulari.name> writes:

> Invoking `guix environment guix`, I found this collision alarming. Do
> you think it's a problem?
>
> I ran `guix pull` yesterday or the day before. Is there a way to
> determine the git commit that corresponds with this version of Guix?
>
> I added the line breaks.
>
> warning: collision encountered:
> /gnu/store/agnxzx1yza8ci0a1gz5pds8gdg8qmnz5-ld-wrapper-0/bin/ld
> /gnu/store/dki0v5cvf1mhfz571k622xvzi1nyinl2-binutils-2.25.1/bin/ld 
>
> warning: arbitrarily choosing
> /gnu/store/agnxzx1yza8ci0a1gz5pds8gdg8qmnz5-ld-wrapper-0/bin/ld

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.

      Mark

Message #13 received at 22659-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Mark H Weaver <mhw <at> netris.org>
Cc: 22659-done <at> debbugs.gnu.org
Subject: Re: bug#22659: Collision of /bin/ld
Date: Tue, 16 Feb 2016 14:59:23 -0500

On Mon, Feb 15, 2016 at 10:46:19PM -0500, Mark H Weaver wrote:
> Leo Famulari <leo <at> famulari.name> writes:
> 
> > Invoking `guix environment guix`, I found this collision alarming. Do
> > you think it's a problem?
> >
> > I ran `guix pull` yesterday or the day before. Is there a way to
> > determine the git commit that corresponds with this version of Guix?
> >
> > I added the line breaks.
> >
> > warning: collision encountered:
> > /gnu/store/agnxzx1yza8ci0a1gz5pds8gdg8qmnz5-ld-wrapper-0/bin/ld
> > /gnu/store/dki0v5cvf1mhfz571k622xvzi1nyinl2-binutils-2.25.1/bin/ld 
> >
> > warning: arbitrarily choosing
> > /gnu/store/agnxzx1yza8ci0a1gz5pds8gdg8qmnz5-ld-wrapper-0/bin/ld
> 
> 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.

Okay, closing!

> 
>       Mark

Message #16 received at 22659 <at> debbugs.gnu.org (full text, mbox):

From: Chris Marusich <cmmarusich <at> gmail.com>
To: 22659 <at> debbugs.gnu.org, leo <at> famulari.name, Mark H Weaver <mhw <at> netris.org>
Cc: 22659-done <at> debbugs.gnu.org
Subject: Re: bug#22659: Collision of /bin/ld
Date: Wed, 17 Feb 2016 17:35:48 +0000

[Message part 1 (text/plain, inline)]

> 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?

[Message part 2 (text/html, inline)]

Message #22 received at 22659-done <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich <at> gmail.com>
Cc: Mark H Weaver <mhw <at> netris.org>, 22659-done <at> debbugs.gnu.org,
 leo <at> famulari.name, 22659 <at> debbugs.gnu.org
Subject: Re: bug#22659: Collision of /bin/ld
Date: Sun, 21 Feb 2016 23:17:32 +0100

Chris Marusich <cmmarusich <at> gmail.com> skribis:

>> 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?

The choice matters, indeed, but it’s deterministic: the first one wins.
And in this case, the first one is the wrapper.

Now, it might be best for ‘guix environment’ to silence these warnings.

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.