Anders Karlsson
I remember slating RedHat quite viciously about the stunt they pulled with gcc 2.96 where they had to eventually release a kgcc just to prevent the sig11 errors. I believe the time has come to give SuSE a rap on the knuckles for not making a gcc_old available in SLPro 8.2 so that people can build solid kernels.
There is a *big* difference! 2.96 was based on a snapshot of the gcc development tree, while our 3.3 is, as 'gcc --version' shows, a prerelease version which we hoped would have been released by the time the masters were ready to be shipped to the plant.
Granted, most of the system might have been compiled with gcc 3.3,
Neither might nor most. Our automatic build system makes sure *all* packages are compiled by the same compiler.
Please SuSE, by all means go cutting edge, but leave something around so people can take one step back from the edge should it not fully work as intended...
There was *no* way around using 3.3. The improvements where too big to be ignored and we definitely needed it for the AMD64 platform. Believe me, maintaining different versions of a compiler in parallel is a nightmare!
Right, that's my rant over. I do have asbestos pants on, so let the flames begin... ;-)
Grab 3.3 release from /pub/projects/gcc/8.2 on ftp.suse.com or its mirrors and try again :) Philipp -- Philipp Thomas work: pthomas@suse.de private: philipp.thomas@t-link.de