| 1 |
Hi ! |
| 2 |
|
| 3 |
another "hardcore" solution could be to create a chroot fresh |
| 4 |
installation whithin you import your system's preferences: |
| 5 |
|
| 6 |
- Create directory |
| 7 |
- Untar last hardened stage 3 |
| 8 |
- Copy your /etc in the chroot |
| 9 |
- Copy your world file in the chroot |
| 10 |
- Copy any kind of data or local aplication to your chroot |
| 11 |
- chroot and update your system |
| 12 |
- when things is done, test it |
| 13 |
- wipe your old gentoo and move your chrooted one on / |
| 14 |
|
| 15 |
|
| 16 |
that's "hardcore" but permit me several times to ressucite a old gentoo |
| 17 |
system. |
| 18 |
|
| 19 |
IF you can't do it, the normal way is: |
| 20 |
|
| 21 |
- Recompile your toolchain by compiling twice this ports: |
| 22 |
virtual/portage virtual/os-headers sys-libs/glibc sys-devel/binutils-config sys-devel/binutils sys-devel/gcc-config |
| 23 |
(don't forget to switch your gcc on the way and to clean your ccache if you use it) |
| 24 |
- Recompile your system (emerge -Davut system) |
| 25 |
- Finally recompile your world. |
| 26 |
|
| 27 |
|
| 28 |
TIPS: use of revdep-rebuild and lafilefixer could help on the way... |
| 29 |
|
| 30 |
|
| 31 |
Hoping that could help you to update your old gentoo. |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
On Wed, 2011-06-15 at 10:55 +0000, Krlis Repsons wrote: |
| 38 |
> Hi all, |
| 39 |
> |
| 40 |
> I've got a machine, which hasn't been upgraded for some 2 years or less. It |
| 41 |
> has GCC-4.3.4 and now I tried to upgrade to 4.5.2, but something failed. So |
| 42 |
> I'm here to ask for the right sequence of upgrades and other actions before |
| 43 |
> it's too late... |
| 44 |
> |
| 45 |
> These actions done already: |
| 46 |
> 1. updated binutils, |
| 47 |
> 2. updated glibc, |
| 48 |
> 3. unmerged and re-emerged libtool (had a blocker), |
| 49 |
> 4. tried with the new GCC, but failed with some unclear problems, |
| 50 |
> 5. switched to vanilla GCC and now compile glibc... |
| 51 |
> |
| 52 |
> So have I done something bad or what should I do to be sure that the upgrade |
| 53 |
> goes as smooth as possible? Thanks... |
| 54 |
|
| 55 |
-- |
| 56 |
-------------------------------------------------------------------------------------- |
| 57 |
Jean-Franois Maeyhieux |
| 58 |
-------------------------------------------------------------------------------------- |
| 59 |
PGP Public Key - Key ID = 63DB4770 Tuttle (JFM) <b4b1@××××.fr> |
| 60 |
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x63DB4770 |
| 61 |
-------------------------------------------------------------------------------------- |
Archives