Kraus Philipp writes:
> I run in a virtual machine a gentoo (~x86) system. I synced the portage
> tree at the weekend an run emerge --update
>
> The update runs without errors, but emerge installed the gcc 4.3.4,
> but on the system is the 4.4.3 installed
>
> [ebuild NS ] sys-devel/gcc-4.3.4 [4.4.3] USE="hardened mudflap nls
> nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -fortran -
> gcj -gtk (-libffi) (-multilib) -multislot (-n32) (-n64) -nocxx -nopie -
> objc -objc++ -objc-gc -test -vanilla"
>
> After the update I run "emerge --depclean" and the 4.3.4 is unmerged
> and now
> I run emerge --update the gcc should installed again
[...]
> Can anybody help me to fix the gcc problem? I only need the 4.4.3 gcc
I do not understand this, but anyway: Add the -t / --tree option you your
emerge command, I guess then you can see which package pulls in the old
gcc. I assume that something needs the old gcc for building, but when it
is built, the old gcc is no longer needed, so emerge --depclean will
remove it.
Do you have "--with-bdeps y" in your EMERGE_DEFAULT_OPTS in make.conf?
Otherwise this should not happen. And if it is set like this, depclean
should not remove it. Hmmmmmm.
You could also emerge -n sys-devel/gcc:4.3 in order to add it to your
world file. Depclean would not remove it then. No real solution, but it
would spare you the emerges. Or you build a binary package with quickpkg,
and use the -k option to emerge, so it will emerge the binary instead of
building from scratch every time.
Wonko
