Throw away those weird gcc-3.1.1-patches!

[Ypsilon]

I had tried it very often with many different CFLAGs.
But bootstrap.sh had always failed.

So because bootstrap always failed with gcc-3.1, I edited package.mask and bootstrap.sh and tried it with gcc-3.1.1-20020701.
It still failed.

This morning, I saw that gcc-3.1.1-final was out, so I decided to try everything again.
I reformatted my partition, downloaded the portage tree and so on.
Then I edited gcc-3.1.1.ebuild and digest-gcc-3.1.1
so that emerge would use the final-gcc-3.1.1 for bootstrap instead of the gcc-3.1.1-20020701- prerelease.

While browsing the ebuild in my editor,
I saw many RedHat- SuSE- and Mandrake-Patches which should be applied to gcc-3.1.1 per default.
I wondered wheter applying so many patches to a bugfix-release of an application like gcc was a good idea,
and finally I commented out all the patches from the gcc-3.1.1.ebuild.

Now I'm sitting here in front of my shiny optimized stage2-gentoo-system that was on the first attempt built without any errors using an original unpatched gcc-3.1.1, after it had failed 10 times with a patched gcc.

So what's the moral of this story...?
_________________
gentoo ownz.

[neuron]