ну поплеры я удалил)))

# emerge gambas
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Starting parallel fetch

>>> Emerging (1 of 3) kde-base/kdelibs-3.5.10-r6
* kde-3.5.9-seli-xinerama.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* kdelibs-3.5-patchset-15.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* kdelibs-3.5.10.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]

* On some setups, which rely on the correct update of utmp records, not using
* utempter might not update them correctly. If you experience unexpected
* behaviour, try to rebuild kde-base/kdelibs with utempter use-flag enabled.

^C

Exiting on signal 2
* The ebuild phase 'setup' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.

>>> Failed to emerge kde-base/kdelibs-3.5.10-r6, Log file:

>>> '/var/lib/entropy/logs/kde-base:kdelibs-3.5.10-r6:20090621-191318.log'