On 8/21/06, Stefan G. Weichinger <[EMAIL PROTECTED]> wrote:
Richard Fish schrieb:
> or "emerge -e world" to complete. I would be tempted to just change
> the flags and hold off on recompiling everything until the next
> version of gcc comes out.
( ... "next version" in terms of minor- or major-version?)
Gcc version numbers are in the form of X.Y.Z, so at a change in X or
Y. The .Z changes should be just bug-fixes. The sad thing is that,
due to changes in the C++ library, it is commonly to recompile all C++
applications when a new version of gcc comes out. And even if it
isn't strictly /necessary/, an emerge -e world is considered the safe
way to handle a gcc upgrade.
I see the point in this. (AFAIK there is no way to break up "emerge -e
xy" into smaller pieces, something to do in several separated steps.
Actually there is. You can find all packages not compiled with -Os
and rebuild them with something like:
cd /var/db/pkg
for pkg in */* ; do
grep -v -- "-Os" $pkg/CFLAGS >/dev/null
test $? -eq 0 && emerge --oneshot =$pkg
done
From your posting I conclude that it also won't do any harm to re-emerge
selected parts with new CFLAGS?)
Correct.
Apart from this I have enough computer-related experience to know that I
simply should be happy with the
luks-encrypted/cpufreq'ed/hibernating/etc. gentoo-system I now have at
hand, instead of spending numerous hours to gain minimal speedups.
Hrm, I also have the experience, but apparently not the good sense.... :-P
-Richard
--
gentoo-user@gentoo.org mailing list
