| 1 |
On 24/01/2014 02:01, Silvio Siefke wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> ok the version 3.3 run without problems, i think the 3.4. make troubles |
| 5 |
> and the package Maintainer from Gentoo has hardmasked. |
| 6 |
|
| 7 |
|
| 8 |
llvm-3.4 is not hardmasked. It is marked ~x86 which is something very |
| 9 |
different. |
| 10 |
|
| 11 |
The mistake you made is using --autounmask-write |
| 12 |
That feature writes local package.unmask entries to satisfy dependencies. |
| 13 |
It's a very blunt tool, it blindly keywords whatever it thinks it needs |
| 14 |
to and when it goes wrong, it goes very wrong quickly. |
| 15 |
|
| 16 |
You are running x86. If you want a package that is marked ~x86 then you |
| 17 |
need to take very careful note of everything that must be keyworded to |
| 18 |
build that package. If you want something basic like llvm that will |
| 19 |
cause many other packages to be upgrade with it, then you need to be |
| 20 |
especially careful. |
| 21 |
|
| 22 |
--autounmask-write is not an intelligent tool. It's not like the stable |
| 23 |
tree which receives testing and you can mostly trust portage because the |
| 24 |
combination has been tested. What it does is throw a bunch of untested |
| 25 |
combinations into the mix and leave you hoping that it might work out. |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Alan McKinnon |
| 31 |
alan.mckinnon@×××××.com |
Archives