unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: carl hansen <carlhansen1234@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: Fwd: warning: collision encountered
Date: Thu, 28 Jan 2016 21:46:48 -0800	[thread overview]
Message-ID: <CAHEkXCSr1JNe4o3-_bZky6tayfPQ8jn2NmKsJj_NQsiM3peMNA@mail.gmail.com> (raw)
In-Reply-To: <20160129034442.GA1694@jasmine>

[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]

On Thu, Jan 28, 2016 at 7:44 PM, Leo Famulari <leo@famulari.name> wrote:

> On Thu, Jan 28, 2016 at 05:24:36PM -0800, carl hansen wrote:
> > resent
> > ---------- Forwarded message ----------
> > From: carl hansen <carlhansen1234@gmail.com>
> > Date: Thu, Jan 28, 2016 at 5:21 PM
> > Subject: warning: collision encountered
> > To: guix-help@gnu.org
> >
> >
> > I get
> > warning: collision encountered: ...
> > warning: arbitrarily choosing /gnu/store/89
> > messages,
> > What do they mean? and How to fix?
>
> Does this explanation make sense?
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22402#37
>
> If so, then you should read the warnings and investigate which files are
> colliding. Some, like the hicolor icon-theme.cache, seem harmless to me,
> although I welcome a second opinion.
>
> [...]
>
> > 13985 warning: collision encountered:
> > /gnu/store/wfvxxpdhnzd59vkad1zasm4f858giv9a-gcj-4.9.3/lib/libatomic.la
> > /gnu/store      /rsgg9a3kwivqszsydvan8pbpdq9ivar5-gccgo-4.8.5/lib/
> > libatomic.la /gnu/store/0bz73dnv3yyiff0fgph9c8lvjz919cl1-gcc-bo
> > otstrap-0/lib/libatomic.la
> > 13986 warning: arbitrarily choosing
> > /gnu/store/wfvxxpdhnzd59vkad1zasm4f858giv9a-gcj-4.9.3/lib/libatomic.la
> > 13987 2354 packages in profile
>
> I don't know about this one. Files the .la extension are used by libtool
> but I don't have enough experience with libtool or know enough about
> libatomic to know if this is going to be a problem.
>

Yes this is a continuation of my previous question. Thanks for response. I
didn't
show the complete output. But I tried to show there are 13987 LINES in the
error
messages. It's not so much the particular cases, it's Why is this happening
at all?
Did I do smething wrong or is this software error? ANd, what is the proper
procedure to
removal of one of the options?
Is it something like:   <http://libatomic.la>
guix package -r /gnu/store/wfvxxpdhnzd59vkad1zasm4f858giv9a-gcj-4.9.3/lib/
libatomic.la
or is it
guix package -r /gnu/store/wfvxxpdhnzd59vkad1zasm4f858giv9a-gcj-4.9.3
or is it
guix package -r / gcj
And can it be done globally?
THere must be something I'm not doing correctly.

[-- Attachment #2: Type: text/html, Size: 3831 bytes --]

  reply	other threads:[~2016-01-29  5:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHEkXCQCi=TxZGDfDJMoaFcjVFmueKd9pr1CPhCvVfim-kiJOA@mail.gmail.com>
2016-01-29  1:24 ` Fwd: warning: collision encountered carl hansen
2016-01-29  3:44   ` Leo Famulari
2016-01-29  5:46     ` carl hansen [this message]
2016-01-29  6:22       ` carl hansen
2016-01-29  8:09         ` Leo Famulari
2016-01-29  7:42       ` Leo Famulari
2016-01-29  7:25   ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHEkXCSr1JNe4o3-_bZky6tayfPQ8jn2NmKsJj_NQsiM3peMNA@mail.gmail.com \
    --to=carlhansen1234@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).