Re: [gentoo-amd64] LLVM Emerge Conflict

2014-01-18 Thread Barry Schwartz
Frank Peters skribis: > Llvm is used for the gallium part of mesa. So won't this require > excluding the gallium use flag as well? I don’t know. I updated LLVM so I could maintain my Pure language ebuilds. Otherwise I am not a big fan of clang and so forth.

Re: [gentoo-amd64] LLVM Emerge Conflict

2014-01-18 Thread Frank Peters
On Sat, 18 Jan 2014 19:29:43 -0600 Barry Schwartz wrote: > > llvm < 3.4 is specified for the llvm use flag in mesa. > That does explain things. Llvm is used for the gallium part of mesa. So won't this require excluding the gallium use flag as well? I don't use high-end graphics on my system

Re: [gentoo-amd64] LLVM Emerge Conflict

2014-01-18 Thread Barry Schwartz
Frank Peters skribis: > Subject: [gentoo-amd64] LLVM Emerge Conflict > From: Frank Peters > 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 get

[gentoo-amd64] LLVM Emerge Conflict

2014-01-18 Thread Frank Peters
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