🚀 go-pugleaf

yschoe@schoch.che.utexas.edu (Yoonsuck Choe) writes:

>Dear Gcc gurus:
>
>I am trying to install gcc-2.7.0 on a DEC alpha running OSF/1 3.2 with
>gcc-2.6.3 already installed and running.
>
>I don't want to mess up with the previous 
>installation - i.e., I want to make sure that the old one is still
>there up and running even if I fail in compiling gcc-2.7.0 correctly 
>in the first place.
>
>[Q1]
>Does gcc-2.7.0 make takes care of this? I mean does it write over the
>old one or, creates a new tree if it finds a previously installed one?

Mostly it creates a new tree, but it does write over some files.
It writes over the info documentation files, the man page, and over the
files in the bin directory, i.e. the `gcc' compiler driver executable.
However, you should be able to use the new `gcc' driver to invoke
the old compiler using the -V 2.5.8 option.

>[Q3] if I choose to install the new versino in a separate tree, 
>can I accomplish this by just setting the 'prefix' to a 
>path different than before?

Yes.

-- 
Fergus Henderson             	WWW: http://www.cs.mu.oz.au/~fjh
fjh@cs.mu.oz.au              	PGP: finger fjh@128.250.37.3
ObQuote: "... in general, safety is not very high on the lists of concerns
  of the [C++] committee members ... After all, if you want semantically
  safe languages that are fundamentally different from C, you don't have
  to look very far." -- Andrew Koenig, editor of the draft C++ standard.