public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] LLVM Emerge Conflict
Date: Sat, 18 Jan 2014 19:29:43 -0600	[thread overview]
Message-ID: <20140119012943.GA14566@crud> (raw)
In-Reply-To: <20140118195137.643cf1b21dd2aaf9bde8006e@comcast.net>

Frank Peters <frank.peters@comcast.net> skribis:
> Subject: [gentoo-amd64] LLVM Emerge Conflict
> From: Frank Peters <frank.peters@comcast.net>
> Reply-to: gentoo-amd64@lists.gentoo.org
> Date: Sat, 18 Jan 2014 19:51:37 -0500
> To: gentoo-amd64@lists.gentoo.org
> 
> Hello,
> 
> Each time I do a world update, I keep getting a message from portage
> which I can't decipher:
> 
> 
> WARNING: One or more updates have been skipped due to a dependency conflict:
> 
> sys-devel/llvm:0
> 
>   (sys-devel/llvm-3.4::gentoo, ebuild scheduled for merge) conflicts with
>     <sys-devel/llvm-3.4[abi_x86_64(-)] required by (media-libs/mesa-9.2.5::gentoo, installed)
> 
> 
> This message only apears when I do "emerge -pvDu world."  If I do a direct
> "emerge -pvDu llvm" then no conflict message will show.
> 
> Can anyone shed some light on this?

llvm < 3.4 is specified for the llvm use flag in mesa. So I turned off
that flag.



  reply	other threads:[~2014-01-19  1:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19  0:51 [gentoo-amd64] LLVM Emerge Conflict Frank Peters
2014-01-19  1:29 ` Barry Schwartz [this message]
2014-01-19  2:00   ` Frank Peters
2014-01-19  2:24     ` Barry Schwartz

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

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

  git send-email \
    --in-reply-to=20140119012943.GA14566@crud \
    --to=chemoelectric@chemoelectric.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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