Could someone please consider this idea I listed in the forums in regards to the GCC ebuild: http://forums.gentoo.org/viewtopic-t-316883.html ? Many thanks :).
This is already in place. It was forgotten in some/one ebuild of gcc once. As far as I'm been able to track. /sbin/fix_libtool_files.sh ${OLD_GCC_VERSION} ${OLD_GCC_CHOST} are present in most of the ebuilds. RESOLVED INVALID ?
It's present in the older ebuilds, but strangely enough it seems to have been removed for some odd reason. Why? bash-2.05b$ grep OLD_GCC gcc-3.4.3.20050110-r1.ebuild bash-2.05b$ grep OLD_GCC gcc-3.4.3-r1.ebuild bash-2.05b$ grep OLD_GCC gcc-3.3.5-r1.ebuild bash-2.05b$ grep OLD_GCC gcc-3.3.5.20050130-r1.ebuild bash-2.05b$ grep OLD_GCC gcc-3.3.5.20050130.ebuild # no output = no match =o!
I take that back; it's been inconsistently added to 2.95, 3.1.1 3.2.3, 3.3.2, 3.3.5, and 3.4.1.
it's in the eclass
Ok, I'll look into it a but closer.
Seems like someone may have made an interesting discovery: http://forums.gentoo.org/viewtopic-t-318791-start-50.html And I quote: 'I tried it (stage1) and I can confirm this. For about a week I didn't have ebuilds which didn't compile at all (however, some smaller missing dependencies which could be found quickly by looking at the error messages). After all I probably found the "disturbing element". It seems that during gcc update (while installing from scratch with stage1/2) the file /etc/env.d/05gcc-i686-pc-linux-gnu ist left behind, containing the evil path (/usr/i386-pc-linux-gnu/gcc-bin/3.3.5). There is a (correct) 05gcc file, which is about 2 hours younger. So I guess the ebuild "forgot" to delete 05gcc-i686-pc-linux-gnu. On the "clean" system from stage1 install this doesn't matter, but maybe for the stage3 installation it did...'
