save your .config, run
# make mrproper
in kernel dir, copy .config back and run
# make
afterwards

app-office/scribus would be one important one depending on qt:3

app-mobilephone/moto4lin
app-office/qbankmanager
dev-util/valkyrie
net-voip/twinkle
would probably be missed more or less...
games-simulation/kfreeflight a bit....

...others i've gotten rid of already, though some are missed much ...

just put dev-tex/texlive-core (and 'required' packages) in /etc/portage/profile/package.provided and use tlmgr to install your texlive
will texlive be kept to date if I do so?

In this case portage will not look at any texlive pieces you've put into the package.provided file, so updating (and ...

CoderMan wrote: Sorry, forgot to mention: all paritions and logical volumes are XFS.

XFS is never fsck'd on my system, since the fsck.xfs is just a placeholder to tell you to use xfs_check or xfs_repair to do the job. So I wonder what's wrong with your system that your XFS partitions are fsck'd by a placeholder?

VoidMage wrote:If portage uses wrong one, then most probably
your java environment is messed up.

From my experience the java setup needn't be messed up for portage to chose a wrong JDK, but if you say so it's probably true.(?)

I've encountered this problem today and its really bugging me....

[...]
>>> Emerging (1 of 2) net-libs/xulrunner-1.9.1.5
* firefox-3.5.5.source.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* xulrunner-1.9.1.4-patches-0.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild ...

If you want to let tlmgr manage everything (not that i know tlmgr well), assume a multi user system with many people using latex. Whether everyone needs root access on the system to use the tlmgr or all packages will only be installed locally for every user so many packages are duplicates? Root ...

I'm using latex myself too, up till now I've not yet had problems with the texlive ebuilds in portage. For very special requirements (tex files from other people who are using 'strage' classes) I put the required classes tohether with the .tex files so they are used instead of the global ones. But ...

-march=core2 -mtune=generic is counter productive. Use -march=native.

Either way, the atom is i686. The fit-pc1 had a i586 geode, so that's why the article says to use i586 CHOST.

The atom, indeed, is i686, so i686 CHOST should be used.
But, since gcc doesn't yet know the atom scheduling it's ...

I'm running an atom with -march=core2 -mtune=generic since the features it supports are the same as the generic core2 architecture, but since it only uses in-order execution of microops (compared to out-of-order execution in core2) it's (should be) best to tune to a generic (or pentium) architecture ...

You seem to be missing the i915 kernel module, which is required for DRM.
In you kernel config (make menuconfig) go to
Device Drivers -> Graphics Support -> Direct Rendering Manager -> Intel 830M, 845G, 852GM, 855GM, 865G
(activate the modules necessary)
and select the i915 driver whether as module ...

If you are still using KDE3, it's about time to switch since KDE3 is about to be removed from Portage.
Or moved into a overlay, it's not maintained anymore (by upstream or gentoo).


KDE4 became usable just now (but still far from good, compare e.g. amarok functionality) so the first thing to be ...

I don't know if Linux supports the Marvel controller in RAID mode at all, so no guarantee given. About your Marvell bios RAID, I don't know if it can be recognized at all, dmraid should do the job for all supported software (fakeraid) raid setups. If you want to try the Marvell provided driver you ...

Your problem is not really the compiler version or some ABI changes but changes to the C++ library (libstdc++) included in gcc (or better g++). Those libraries are versioned so trying to run a c++ program linked to the new version (4.3 in your case) will not work when the available version (by means ...

The in-kernel drivers support the marvell chip in legacy mode, so bios should be set to legacy mode. the sata ports will be handled by the ahci driver, so it's necessary to have this one too. I've built support for both, the ahci and marvell driver into the kernel and the pata and all 4 sata (2 ...

The mv_thor is the driver Marvell supplied. The ahci driver supports the sata ports for quite a while now, the 'Marvell PATA support via legacy mode' driver (mv ?) supports the parallel ata ports of this chip now, so the Marvell provided driver is no longer necessary but everything is working with ...

The current kernel contains all necessary drivers, the ahci driver and the marvell pata driver will support those chips now, so the marvell driver is no longer necessary.

you probably updated qt:3 so you need remerge kdelibs:3.5 to get kde working again

you should not try to upgrade via emerge -pv world but use emerge -avuD world or -avuND world. This will update all deep dependencies too.
And, especially have portage up-to-date too, before you attempt to update!

...probably...
Maybe check with qfile (portage-utils) which package they belong to, but very likely you can delete them all :D
After cleaning the env.d dir it should be alright already, at least no more broken compiler and such.
Check the gcc/binutils directories, it should be very obvious if they ...

You're probably hitting a problem i discovered some time ago when i set up a system starting from a stage1.
There, when unmerging the pre-stage1 gcc during bootstrap it left some files, dirs and symlinks in /usr/gcc or /usr/lib (don't remember exactly anymore) and /etc/env.d(/gcc)?, which cause the ...

1st post on page 2: http://forums.gentoo.org/viewtopic-p-54 ... ml#5473076
You probably got the set or something alike? So you need to comment out qt-phonon sind it's blocking phonon from kde.

Hwoarang wrote: make sure to comment out qt-phonon otherwise you will have conflits with media-sound/phonon

...how 'bout this?

Hwoarang wrote:ccache should give you an extra boost

Sure it does, it only took like... 10..15 minutes on 3 GHz clocked Q9450

Thanks for the set, i now see i was missing qt-assistant
Although it's reinstalling all already installed qt packages instead of only adding/updating the missing ones it's alright.