From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A52A7138247 for ; Sun, 19 Jan 2014 02:00:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 746D4E0AC1; Sun, 19 Jan 2014 02:00:42 +0000 (UTC) Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by pigeon.gentoo.org (Postfix) with ESMTP id C695DE0AAA for ; Sun, 19 Jan 2014 02:00:41 +0000 (UTC) Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta08.westchester.pa.mail.comcast.net with comcast id FdtR1n0011c6gX858e0hSA; Sun, 19 Jan 2014 02:00:41 +0000 Received: from ajax ([24.11.47.14]) by omta23.westchester.pa.mail.comcast.net with comcast id Fe0h1n0070JMh7c3je0h87; Sun, 19 Jan 2014 02:00:41 +0000 Date: Sat, 18 Jan 2014 21:00:34 -0500 From: Frank Peters To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] LLVM Emerge Conflict Message-Id: <20140118210034.e366d7bdc1707c46837e276e@comcast.net> In-Reply-To: <20140119012943.GA14566@crud> References: <20140118195137.643cf1b21dd2aaf9bde8006e@comcast.net> <20140119012943.GA14566@crud> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.22; x86_64-unknown-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1390096841; bh=Zj1U2Nm9FugznON2ZztUz6/z0zZp1OM7E9CSXFyn43A=; h=Received:Received:Date:From:To:Subject:Message-Id:Mime-Version: Content-Type; b=W6KpX87nfQnG4gqhZEtCppUyK1enpAW9wqeTcJKj0a7cxZDkNB7HfPzWDEqem93wI 4D4UyRGCsqu6cqQIG4yXXzXE0ZJ1BZaXKFYK+fJG9yjdiSjKTfv2uNrNPAHj6dEaqR KoIum+hsw5wC80zycstoiAxoo9RoA+udnO/TAwR1bnzYYSyUX4uRrSCL1C4Sm5T7Td Y+yV8vtvIMZ5kMdO8W+1vLEzJhQ/TcS8NEXkYtOKewfvrL1njqVBD4+CdZWLfJEVgg mZEeLxEK+pEMHU6f7gOgEG2V2CCoHLLPx9IHsSpyARcEq3mWgRT2FOCG/YTd3GNnkC iMU2E/2Ql5OkQ== X-Archives-Salt: f4c88cbb-1e71-4729-90fe-b2bcd9283443 X-Archives-Hash: 498336a498847feb6b976adc12704d6d 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 but I recall that some time ago I had problems with other stuff if I omitted the gallium and llvm use flags on mesa. Otherwise I'd eliminate gallium entirely. At that time, I didn't question the reason because I didn't need to know and I didn't really care as long as everything worked. This condition can only be temporary as future releases of mesa will likely use llvm >= 3.4. Since on my system llvm is not used for anything else other than mesa gallum, I'll just leave things as they are. Frank Peters