Re: 'gcc -V' no longer works properly between 2.95 and older versions

[Michael Deutschmann <michael at talamasca dot wkpowerlink dot com>]

On Fri, 13 Aug 1999, Mike Stump wrote:
> Yeah, I've been saying that for the last half decade.  -V isn't
> useful, it does nothing worthwhile, don't ever use it.  Install with a
> prefix that is unique, has the package name, and the version number in
> it, and you will never go wrong.

I disagree with that.  

First, I've been using "gcc -V 2.7.2.3" for Linux kernel compilations all 
through my 2.8.1 installation and it worked *fine*.  Only 2.95 introduced 
a problem.

Changing the prefixes is messy, and can apparently lead to extra work
(see the FAQ, which endorses your method, but admits that it can require
intervention to find the binutils.)

In contrast, the only problem with the '-V' method is if incompatible 
changes are made to the specs format.  While this has happened -- I think 
there's a good chance it can be resolved.  Zack's posting suggests that 
the specific breakage was accidental.

Even assuming it can't be fixed, it's still possible to use one "gcc"
binary for new gcc, and a "gcc-old" for all older compilers.  I don't
want to do that if I don't have to, but it works and does *not* require
using a different prefix. 

---- Michael Deutschmann <michael@talamasca.wkpowerlink.com>