This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc -v
- To: Joe Buck <jbuck at racerx dot synopsys dot com>
- Subject: Re: gcc -v
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 18 Jan 2001 14:16:49 +0100
- Cc: gdr at codesourcery dot com (Gabriel Dos Reis), gcc at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <200101180737.XAA05774@racerx.synopsys.com>
Joe Buck <jbuck@racerx.synopsys.com> writes:
| > Is there any technical reason why "gcc -v" should output to stderr and
| > not to "stdout"? I'm in the process of adding (finally!) the new style
| > DejaGnu framework for V3 and I'm finding that "feature" to be
| > annoying as something like (the following which ran successfuly is
| > reported as a failure)
| >
| > set output [remote_exec host $libstdcxx_options(CXX) -v]
| >
| > AFAICT, we should only use stderr for diagnostics, not for normal
| > behaviour.
|
| gcc --version prints on stdout (but it prints only the version number).
Yes, I know that but gcc -v gives much better.
From what I understand from the the code in gcc.c, "gcc -v" -- with no
additional arguments" is intended to give enhanced "gcc --version".
Anyway, after the freeze is removed I'll try to address that
issue. It is not critical.
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com