Unmerged gcc

[blubber]

Hi,
I accidently enmerged gcc :'(. I was trying to compile HAL9000, wich needs GCC 2. So I emerged GCC 2. After HAL9000 was compiled I tried to merge GCC 3 again, but that didn't work. So I tried to umerge GCC 2, using emerge unmerge gcc. But that would emerge GCC 2 and 3 so I broke off the unmerge in time. The next thing I did was ebuil gcc-2.95.3-r7 unmerge, that unmerged GCC 2, but it also rendered GCC 3 useless. The whoole gcc binary is gone, is there any way to restore this, or should I start the whole installation again?

This is the output from emerge -s gcc

[pjp]

Do you emerge with the binary option? If you do, there's a binary package in /usr/portage/packages/All/ . You could use emerge to install that binary pacakge.
_________________
Quis separabit? Quo animo?

[blubber]

I emerged everything from source. Why would I need GCC if I used binaries?

[pjp]

If you emerge with the binary option, it creates a binary. That way, you don't have to compile something every time you install it. Plus, it helps with recovery. 'man emerge' explains the option.
_________________
Quis separabit? Quo animo?

[blubber]

ow, ok But that doens't solve my problem. It's just so stupid of me to unmerge GCC ... I certainly learned my lesson

[rac]

I think your best bet is to unpack a stage 1 tarball across your root filesystem. Re-emerge any packages that give you trouble afterwards.
_________________
For every higher wall, there is a taller ladder

[blubber]

Yeah, my idea was to just boot the gentoo cd and bootstrap again. Ofcourse saving all config files first, you never know

[blubber]

Well, I upkaced the stage 1 tarball on my sytem, GCC is back, but it still doesn't work asa good as before. I'm no emerging -e system to fix the damn thing..