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: law at cygnus dot com
- Subject: Re: A patch for g77spec.c
- From: Craig Burley <burley at gnu dot org>
- Date: Sun, 21 Jun 1998 21:04:34 -0400 (EDT)
- CC: hjl at lucon dot org, egcs-patches at cygnus dot com
> In message <m0yn5PP-00026CC@ocean.lucon.org>you write:
> > Hi,
> >
> > This patch fixes
> >
> > # g77 -v
>More specifically it prevents "g77 -v" from trying to build and link
>a non-existant program. I'd noticed we'd regressed in this regard
>recently, but hadn't had the chance to look at the problem.
>
> > Fri Jun 19 07:54:40 1998 H.J. Lu (hjl@gnu.org)
> >
> > * g77spec.c (lang_specific_driver): Check n_infiles before
> > appending args.
>Installed. Thanks!
I'd prefer it if people would respond to bugs by fixing the bugs,
rather than eliminating the functionality that exposes them. I've
thoroughly documented the *desired* behavior of `g77 -v' in the
g77 docs and, IIRC, in a recent email I sent outlining the many
changes I'd been trying to make to the egcs version of g77. In
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.
Why `g77 -v' works for me but fails for others I don't know, but
I doubt the problem is in g77; perhaps in how gcc handles the
specs stuff, but certainly disabling the functionality makes it much
less likely anybody's going to help identify the problem, the main
one being: why isn't `cpp' being found in that situation?
(`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.)
tq vm, (burley)