From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] LLVM Emerge Conflict
Date: Sat, 18 Jan 2014 20:24:17 -0600 [thread overview]
Message-ID: <20140119022417.GA16849@crud> (raw)
In-Reply-To: <20140118210034.e366d7bdc1707c46837e276e@comcast.net>
Frank Peters <frank.peters@comcast.net> 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.
prev parent reply other threads:[~2014-01-19 2:24 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
2014-01-19 2:00 ` Frank Peters
2014-01-19 2:24 ` Barry Schwartz [this message]
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=20140119022417.GA16849@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