We have vintage versions of GCC dating back to version 2.95.3-r9 in portage, but their usefulness is greatly diminished without similiar vintage versions of glibc for use in cross-compiler toolchains. For instance, openmoko uses GCC 4.1.2 and glibc 2.6, but Gentoo is not able to build toolchains for it because glibc 2.6 is missing from the tree. While it is still possible to build cross-compiler toolchains, the binaries will often require symbols provided by the newer glibc, which renders them useless. Would it be possible to introduce ebuilds for glibc 2.6 and a few of the others that died with it 5 months ago back into the tree?
keeping gcc in the tree is useful for developers to check old compiler behavior. you can emerge those on new glibc systems. you cannot emerge old glibc's on newer systems. use the toolchain overlay for the cruft
(In reply to comment #1) > keeping gcc in the tree is useful for developers to check old compiler > behavior. you can emerge those on new glibc systems. you cannot emerge old > glibc's on newer systems. > > use the toolchain overlay for the cruft The older versions of glibc are not available from the toolchain overlay.
