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

[Spider]

Wheehey.
 time for the preliminary upgrade instructions for all those adventurous
souls that dont want to break everything but only something :)


Overview: 
 how to update from gcc 2.95.3 to 3.2 without breaking too much

1) build gcc / glibc /binutils / gettext packages to backup with
  emerge --buildpkg gcc glibc gettext binutils   (all in gcc 2.95.3)

Move theese aside in a place tagged as gcc 2.95.3 .


2) build an replacement gcc systems
change the profile to default-x86-2.0

export USE="-* build"
emerge --buildpkg gcc 
emerge --buildpkg binutils gettext texinfo glibc
unset USE

This will now replace your gcc with one without c++ and other such
things.. "oops" gcc is now gcc 3.2.. thats good.

Now, We remove all traces of gcc, *shudder*  
emerge -C gcc
and install the binary again:
emerge --usepkg gcc

now, next step... we want a fully working and competent gcc, glibc and
other things:

emerge --buildpkg gcc
emerge --buildpkg binutils gettext texinfo glibc

Lovely, a complete gcc 3.2 system installed! and not a trace of gcc
2.95.3's libstdc++ ...  This is the time when you go "oops" and whine a
lot.

or.. is it?

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

Now, you've restored gcc 2.95.3's paths and data, and overwritten the
gcc, g++ and others with those of gcc 3.2

check with /usr/bin/gcc -v
it reports gcc 3.2 for me


Now, edit /etc/env.d/05gcc
add :
LDPATH=/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3

then run "env-update"


now your old c++ code will work again... everything is normal, until ...
soon..


This is as far as I've come today, my system works, c++ code works,
galeon works, blackbox runs. 

Beware though... when you start to mix c++ codes it will probably break
in strange ways.  Solution: recompile :)

 I hope this helps.....


//Spider









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