| 1 |
On Fri, 29 Mar 2013 02:17:18 +0000, Mateusz Kowalczyk wrote: |
| 2 |
|
| 3 |
> > * These packages depend on emul-linux-x86-gtklibs: |
| 4 |
> > dev-util/android-sdk-update-manager-21 (amd64 ? |
| 5 |
> > app-emulation/emul-linux-x86-gtklibs) sys-devel/gcc-4.5.4 (multilib ? |
| 6 |
> > app-emulation/emul-linux-x86-gtklibs) sys-devel/gcc-4.6.3 (multilib ? |
| 7 |
> > app-emulation/emul-linux-x86-gtklibs) sys-devel/gcc-4.7.2-r1 |
| 8 |
> > (multilib ? app-emulation/emul-linux-x86-gtklibs) |
| 9 |
> |
| 10 |
> |
| 11 |
> I have neither ‘amd64’ nor ‘multilib’ set which raises the question of |
| 12 |
> how and why it got onto my system in the first place… I'm still |
| 13 |
> somewhat wary of clobbering something that has ‘gcc’ in its depgraph… |
| 14 |
|
| 15 |
amd64 and multilib are set by your profile, which are you using? |
| 16 |
|
| 17 |
If you're worrind about removing a dep of gcc, which is reasonable, |
| 18 |
quickpkg it first. Then you can unmerge and still get it back without |
| 19 |
needing gcc. |
| 20 |
|
| 21 |
But before you do any of that, wait a few hours and sync again. That very |
| 22 |
often fixes these strange blockers. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Neil Bothwick |
| 27 |
|
| 28 |
Suicidal twin kills sister by mistake! |
Archives