| 1 |
On 05/10/2016 04:03 PM, Alan McKinnon wrote: |
| 2 |
> On 10/05/2016 18:14, Meino.Cramer@×××.de wrote: |
| 3 |
>> |
| 4 |
>> |
| 5 |
>> (sys-devel/gcc-4.4.7:4.4/4.4::gentoo, installed) pulled in by |
| 6 |
>> sys-devel/gcc:4.4 required by @selected |
| 7 |
> |
| 8 |
>> (cross-armv7a-hardfloat-linux-gnueabi/gcc-4.5.4:4.5/4.5::x-portage, installed) pulled in by |
| 9 |
>> cross-armv7a-hardfloat-linux-gnueabi/gcc:4.5 required by @selected |
| 10 |
> |
| 11 |
> It's a hard problem to solve, and portage doesn't really know the |
| 12 |
> solution. It likely knows how to make itself shut up (remove the low |
| 13 |
> version compilers) but that's unlikely to *solve* it. Maybe you really |
| 14 |
> want to have 4.4 and 4.9, portage doesn't know how it can give that to |
| 15 |
> you so it brain dumps everything it's got and tells you to figure it out. |
| 16 |
> |
| 17 |
|
| 18 |
In this case, you explicitly told portage that you want to keep |
| 19 |
sys-devel/gcc:4.4 and cross-armv7a-hardfloat-linux-gnueabi/gcc:4.5 |
| 20 |
installed, as they are in the @selected set (defined by your world |
| 21 |
file). This means that portage's normal resolution mechanism (remove |
| 22 |
the packages that break things) won't work, as that won't satisfy your |
| 23 |
requests (as it knows them to be). I haven't looked into why gcc 4.9 |
| 24 |
blocks older versions now, although I know it didn't always do so. |
| 25 |
|
| 26 |
-- |
| 27 |
Jonathan Callen |
Archives