gcc already present - can I protect old version?

[dave madden]

 =>From: "Robert J. Gooding" <bob@chagall.phy.queensu.ca>
 =>...
 =>I have loaded and unpacked egcs-1.0.1.tar.gz from an ftp site.
 =>
 =>./configure ran and generated a Makefile
 =>
 =>I already have gcc v2.7 (.?.?) on my machine (PP200 running Linux
 =>2.0.30), and do not want to lose this. If I run 
 =>
 =>make
 =>
 =>will I produce a new gcc compiler? I see no reason to not just leave
 =>the old compiler there.
 =>
 =>(I am relying on the generic make, because even though I only want
 =>g77, I am not sufficiently knowledgable on script files, compiler
 =>builders, etc, to sort through the g77-only make procedure - I just
 =>don't want to potentially lose my perfectly good gcc compiler in
 =>the process.)

I asked a similar question here long ago, and Mike Stump taught me The
Way; I understand it well enough to relate it to you.

When you do "configure", specify a prefix directory:

    % ./configure --prefix=/usr/local/packages/egcs-1.0.1

After your "make" succeeds, you can do a "make install" and the entire
compiler in all its gory will be placed in (e.g.)
/usr/local/packages/egcs-1.0.1.  You can then symlink the drivers you
want (g77) into some directory on your path.  This scheme allows you
to have as many flavors of gcc installed as you want.

d.