| 1 |
On Mon, Dec 12, 2011 at 12:32:04AM -0500, Michael Mol wrote |
| 2 |
|
| 3 |
> llvm is pulled in on most of my systems as a dependency of something |
| 4 |
> else. It doesn't conflict with having gcc installed. |
| 5 |
> |
| 6 |
> emerge sys-devel/llvm |
| 7 |
> |
| 8 |
> And try again. If that fixes it, you should file a bug against the |
| 9 |
> specific package failing to build, noting the missing explicit build |
| 10 |
> dependency. |
| 11 |
|
| 12 |
After some testing, and plain old trial-and-error, I discovered that |
| 13 |
it may have been due to me running with USE starting with "-*". I found |
| 14 |
out that... |
| 15 |
|
| 16 |
* emergeing llvm does not help |
| 17 |
* I unmerged llvm, and added the line |
| 18 |
media-libs/mesa llvm |
| 19 |
to /etc/portage/package.use, and the build works. |
| 20 |
|
| 21 |
Now that I know what to look for, I can find... |
| 22 |
https://bugs.gentoo.org/show_bug.cgi?id=377013 |
| 23 |
which covers this issue. The problem is that the generic error message... |
| 24 |
|
| 25 |
configure: error: LLVM is required to build Gallium R300 on x86 and x86_64 |
| 26 |
|
| 27 |
...is not informative enough. This has been fixed in mesa 7.12, due out |
| 28 |
in a few months. Apparently, it'll generate an error message advising |
| 29 |
that mesa must be built with USE="llvm" if Gallium R300 is to be built. |
| 30 |
|
| 31 |
-- |
| 32 |
Walter Dnes <waltdnes@××××××××.org> |
Archives