Some fixes for problems encountered when installing on CentOS 6.2 (they are not CentOS specific though).
Masking ">sys-devel/gcc-4.2" masks gcc-4.2.4, so portage pulls in gcc-4.1 in stage4, which fails to build due to "march = native", which is only supported for gcc-4.2 and newer. By masking ">=sys-devel/gcc-4.3", gcc-4.2.4 can be installed.
stage2-portage failed since the active Python version was not set
Is ">=sys-devel/gcc-4.3" masked to make sure gcc is compatible with the host OS libc (discussed on gentoo-alt a while ago)? If so, I wonder if newer gcc version work with CentOS 6.2, any experience with this?
Some fixes for problems encountered when installing on CentOS 6.2 (they are not CentOS specific though).
Is ">=sys-devel/gcc-4.3" masked to make sure gcc is compatible with the host OS libc (discussed on gentoo-alt a while ago)? If so, I wonder if newer gcc version work with CentOS 6.2, any experience with this?