1 |
On Tue, 13 Mar 2018 11:36:12 -0600, thelma@×××××××××××.com wrote: |
2 |
|
3 |
> sys-apps/portage:0 |
4 |
> |
5 |
> (sys-apps/portage-2.3.16:0/0::gentoo, ebuild scheduled for merge) |
6 |
> pulled in by sys-apps/portage (Argument) |
7 |
> |
8 |
> (sys-apps/portage-2.3.6:0/0::gentoo, installed) pulled in by |
9 |
> sys-apps/portage[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] |
10 |
> required by (app-portage/gentoolkit-0.3.3:0/0::gentoo, installed) |
11 |
|
12 |
Your old version of gentoolkit (and other packages mentioned in the full |
13 |
output) is causing this. Trying to upgrade an out of date system |
14 |
piecemeal can cause this. Just do an emerge -u @system and let portage |
15 |
resolve these issues rather than trying to do it yourself. |
16 |
|
17 |
|
18 |
-- |
19 |
Neil Bothwick |
20 |
|
21 |
C Error #011: First C Program, huh? |