bug#22659: Collision of /bin/ld

2016-02-21 Thread Ludovic Courtès
Chris Marusich 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-stand

bug#22659: Collision of /bin/ld

2016-02-17 Thread Chris Marusich
> 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 thos

bug#22659: Collision of /bin/ld

2016-02-16 Thread Leo Famulari
On Mon, Feb 15, 2016 at 10:46:19PM -0500, Mark H Weaver wrote: > Leo Famulari 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 tha

bug#22659: Collision of /bin/ld

2016-02-15 Thread Mark H Weaver
Leo Famulari 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. > > war

bug#22659: Collision of /bin/ld

2016-02-14 Thread Leo Famulari
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/stor