Re: [gentoo-dev] Gentoo 1.2 to 1.4 update, HowTo do it and not break everything

[Spider]

begin  quote
On Mon, 12 Aug 2002 20:22:24 -0400
Todd Heim <heim-gentoo@××××××××.net> wrote:

> On Monday 12 August 2002 03:48 pm, Spider wrote:
>
> sounds good.. but a few questions first:
>
> > Now, We remove all traces of gcc, *shudder*
> > emerge -C gcc
> > and install the binary again:
> > emerge --usepkg gcc
>
> why unmerge it, then reemerge the same copy?
To make sure that we wipe all traces of the old gcc when we build the
new "clean" and fully functional version.

the "USE="build" stuff makes sure that /usr/bin/gcc is overwritten, but
doesnt create c++ things,  this will make sure that you have an
"uncontaminated" system which only runs gcc 3.2 when you build the final
gcc, glibc binutils and other things.



 
> > move aside your gcc 3.2 complete binaries, copy in gcc 2.95.3 ones
> > emerge --usepkg =gcc-2.95.3-r7 (whatever version it was you had
> > installed) emerge --usepkg gcc
>
> why emerge 2.95, then 3.2 again?

This is because the old gcc 2.95.3 package had its own /usr/bin/gcc
which you -dont- want right now, you want to simply overwrite the "gcc"
binary with the new one from gcc 3.2 (complete build)



I've ran this for a while, and all packages work neatly, including big
bloats like mozilla and galeon that depend on c++

When you rebuild one c++ thing though, you need to rebuild the things
that depend on it as well as to not get colliding libraries.


A tip: 

for i in /usr/lib/*.so; 
do ldd ${i}|grep "2.95.3" - >/dev/null && qpkg -fv ${i} ;
done

this will list all libraries that depend on c++ from 2.95.3

in my case it was imagemagick, and Mesa from xfree.

then you can scan the binaries, those are more common


//Spider


--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end