* bug#22659: Collision of /bin/ld
@ 2016-02-14 9:12 Leo Famulari
2016-02-16 3:46 ` Mark H Weaver
0 siblings, 1 reply; 5+ messages in thread
From: Leo Famulari @ 2016-02-14 9:12 UTC (permalink / raw)
To: 22659
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#22659: Collision of /bin/ld
2016-02-14 9:12 bug#22659: Collision of /bin/ld Leo Famulari
@ 2016-02-16 3:46 ` Mark H Weaver
2016-02-16 19:59 ` Leo Famulari
0 siblings, 1 reply; 5+ messages in thread
From: Mark H Weaver @ 2016-02-16 3:46 UTC (permalink / raw)
To: Leo Famulari; +Cc: 22659
Leo Famulari <leo@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
^ permalink raw reply [flat|nested] 5+ messages in thread* bug#22659: Collision of /bin/ld
2016-02-16 3:46 ` Mark H Weaver
@ 2016-02-16 19:59 ` Leo Famulari
2016-02-17 17:35 ` Chris Marusich
0 siblings, 1 reply; 5+ messages in thread
From: Leo Famulari @ 2016-02-16 19:59 UTC (permalink / raw)
To: Mark H Weaver; +Cc: 22659-done
On Mon, Feb 15, 2016 at 10:46:19PM -0500, Mark H Weaver wrote:
> Leo Famulari <leo@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
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#22659: Collision of /bin/ld
2016-02-16 19:59 ` Leo Famulari
@ 2016-02-17 17:35 ` Chris Marusich
2016-02-21 22:17 ` Ludovic Courtès
0 siblings, 1 reply; 5+ messages in thread
From: Chris Marusich @ 2016-02-17 17:35 UTC (permalink / raw)
To: 22659, leo, Mark H Weaver; +Cc: 22659-done
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
> 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?
[-- Attachment #2: Type: text/html, Size: 697 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#22659: Collision of /bin/ld
2016-02-17 17:35 ` Chris Marusich
@ 2016-02-21 22:17 ` Ludovic Courtès
0 siblings, 0 replies; 5+ messages in thread
From: Ludovic Courtès @ 2016-02-21 22:17 UTC (permalink / raw)
To: Chris Marusich; +Cc: 22659, 22659-done
Chris Marusich <cmmarusich@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’.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-02-21 22:18 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-14 9:12 bug#22659: Collision of /bin/ld Leo Famulari
2016-02-16 3:46 ` Mark H Weaver
2016-02-16 19:59 ` Leo Famulari
2016-02-17 17:35 ` Chris Marusich
2016-02-21 22:17 ` Ludovic Courtès
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).