This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: A patch for g77spec.c
- To: Craig Burley <burley at gnu dot org>
- Subject: Re: A patch for g77spec.c
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sun, 21 Jun 1998 19:33:20 -0600
- cc: hjl at lucon dot org, egcs-patches at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199806220104.VAA25662@melange.gnu.org>you write:
> I'd prefer it if people would respond to bugs by fixing the bugs,
> rather than eliminating the functionality that exposes them.
Err, I thought it did do the right thing.
g77 version egcs-2.91.41 19980619 (gcc2 ss-980502 experimental) (from FSF-g77 version 0.5.23)
Reading specs from /usr/egcs/lib/gcc-lib/i686-pc-linux-gnulibc1/egcs-2.91.41/specs
gcc version egcs-2.91.41 19980619 (gcc2 ss-980502 experimental)
But now it doesn't try to run f771 and link non-existant code.
> short: `g77 -v' is supposed to produce *thorough* information
> on the version numbers of all the relevant products (the gcc back
> end, the g77 front end, the various libf2c sub-libraries, the
> preprocessor, and so on), and even provide a simple test that they're
> installed correctly.
I don't see how you're going to get information from the backend,
libraries, etc etc without running the backend, running collect2
and other crud. Trying to run the backend to get version information
when there's no input files seems rather wrong to me.
Note that information will still appear if you do something like
g77 -v foo.f
But there's no good way to get it for
g77 -v
Unless you want to embed all the version information in the g77
binary itself.
> (`g77 -v' as I implemented it in egcs/g77 and g77 0.5.23 does *not*
> try to link a non-existant program!! If it does, that's a bug.)
It certainly did for me.
jeff