On Sun, 01 Jan 2012 11:13:16 -0500 Jeff Cranmer <j...@lotussevencars.com> wrote:
> > > > > Jeff > > > > $ qfile libQtGui.so.4.7.4 > > x11-libs/qt-gui (/usr/lib64/qt4/libQtGui.so.4.7.4) > > > > Look at the date time that you built x11-libs/qt-gui (in your > > emerge.log, or use genlop) and compare with said file. > > The files match, last compiled in the morning, two days ago, which is > before I tried my most recent changes. > > Success - Recompilation of this file gets me a k desktop. > > Is there a good way to force-recompile an entire system's code? > emerge -Dav system and emerge -Dav world don't seem to go down far > enough in the hierarchy to recompile all dependencies. That's a common enough problem but there doesn't seem to be much portage can do about it. Lower-level libs can easily trigger a rebuild for ebuilds that depend on them, but the reverse is not true. For example, if you have some KDE app that requires a recent qt version (and your installed qt is some earlier version), then portage can't figure out to tell you to upgrade or rebuild qt because the dependencies are the wrong way round for that. You have to remember yourself when a Qt rebuild might be needed. You can use sets help to help ensure you do rebuild everything in Qt, but you have to remember when to do it. xorg-server has the same issue, and the solution there is also "remember to rebuild the xorg-drivers when you upgrade the X server" -- Alan McKinnnon alan.mckin...@gmail.com
