Sender:	tim AT mxrelay DOT g-net DOT be
Message-ID:	<3B9DAB33.EBF33C94@falconsoft.be>
Date:	Tue, 11 Sep 2001 08:12:03 +0200
From:	Tim Van Holder <tim DOT vanholder AT falconsoft DOT be>
Organization:	Anubex (www.anubex.com)
X-Mailer:	Mozilla 4.78 [en] (X11; U; Linux 2.2.16-3 i686)
X-Accept-Language:	en, nl-BE, nl
MIME-Version:	1.0
To:	Alex Vinokur <alexvn AT bigfoot DOT com>, djgpp AT delorie DOT com
Subject:	Re: gcc, gpp & option -v
References:	<3B9DA231 DOT 4D584808 AT bigfoot DOT com>
Reply-To:	djgpp AT delorie DOT com

Alex Vinokur wrote:
> 
> [snip]
> 
> Some question :
> 1. Why do _both 'gcc -v' and 'gpp -v'_ produce the same output?
Because both compiler drivers choose the compiler based on the
extension;
if you give them a C file, they call the C compiler.

> 2. What is GNU CPP version ... ? (C compiler?)
CPP is the C preprocessor, which handles preprocessor directives
(#define
and the like) and strips comments.

> 3. 'gpp -v a.c' produces _C++ compiler_ version as well.
>    Why doesn't 'gpp -v' do the same ?
Easy - with gcc/gpp -v, you're asking for the compiler driver's version,
which it reports.  With gcc -v <file>, you're asking for verbose
compilation and linking, in which case each component prints its version
information.

> 4. Is there any option that produces _C++ compiler_ version ? :
>    %gpp <?-option>
>    GNU C++ version 2.95.3 20010315/djgpp (release) (djgpp) compiled by
> GNU C version 2.95.3 20010315/djgpp (release).
No - you'll need to do verbose compilation; as a rule though, all gcc
components have the same version (provided no -V, -M or -B options are
used during compilation), so the version reported by gcc -v can be used.

- Raw text -