[SOLVED] Switching to ~amd64 - Remove old gcc?

[anyNiXwilldo]

As I am typing this, I am switching my second (not my main) Hardened system to ~amd64. I've rebuilt the toolchain twice (and used gcc-config to set the new compiler after the first rebuild) and am presently emerging the system. Once I have finished emerging the system (and prior to emerging the world), is it safe to remove the old gcc and keep only the ~amd64 gcc installed? Or do I need to keep both compilers installed because some code won't build with the new one?
_________________
Of course you can have my root password. I'm on Hardened!

[eccerr0r]

For the most part, you can remove the old GCC's. Theyr'e slotted so that means each get their own disk space.

However I'd recommend not removing the latest STABLE version just in case something doesn't compile just right with the testing version... Generally the devs will test against STABLE gcc, and for testing gcc - you're on your own.

I see a lot of people with several copies of stable gcc. Generally that's a waste of disk space. Make sure your gcc-config is pointing to the version you want and emerge --depclean the ones you don't.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[anyNiXwilldo]

Okey dokey. And thanks for the help.
_________________
Of course you can have my root password. I'm on Hardened!

[anyNiXwilldo]

Ugh! Util-linux will NOT build, which means the upgrade to ~amd64 can not happen. Now I remember why I have always destested unstable. I will wipe and reinstall to stable Hardened in a chroot.
_________________
Of course you can have my root password. I'm on Hardened!