No you can't just use the regular SlackBuild as this will cause the new(old) compiler to overwrite the standard version.
AlienBob has a Slackbuild for compiling an alternate version which can be installed alongside of the standard compiler, however, my src2pkg build script installs it in such a way that it will co-exist much better.
As I said, the best way is to configure and install the alternate compiler into its' own prefix which is not part of the normal PATH -inother words do not install it into --prefix=/usr. By configuring and installing into a separate path and then using a wrapper script to run the alternate version, things will run much smoother.
You can build your own if you like, using my src2pkg script from here:
http://distro.ibiblio.org/pub/linux/...vel/gcc-3.4.6/
You need to install src2pkg in order to use that script, though. If you just want the easiest way out, just install this pre-compiled package:
http://distro.ibiblio.org/pub/linux/...4.6-i486-1.tgz
The package installs the the gcc-3.4.6 compiler to prefix=/usr/gcc-3.4.6. But it places a 'wrapper' script in /usr/bin which is called GCC346.
In order to compile sources with the alternate compiler, simply type 'GCC346' before the regular command. For example, to build the kernel-2.4.x sources:
'GCC346 make dep'
'GCC346 make bzImage'
'GCC346 make modules'
'GCC346 make modules_install'
This is the easiest and most dependable way to use an alternate compiler. Other methods require you to manually alter your PATH or create/edit your .bashrc file and may still not work with all sources unless you alter the sources. I use this method to keep 5-6 compiler versions on my system at all times.