[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unparsable gcc version string? [WAS: lily 1.4.15]

From: Jochen Voss
Subject: Re: Unparsable gcc version string? [WAS: lily 1.4.15]
Date: Tue, 2 Jul 2002 18:55:43 +0200
User-agent: Mutt/1.4i


On Tue, Jul 02, 2002 at 12:27:32PM +0200, Jan Nieuwenhuizen wrote:
> AAARG!  How is anyone (being a humble configure script) supposed to
> pick `3.1.1<SPACE>20020606' to be the version string from that?

Just for reference I want to cite the upstream authors opinion
on this.  As gcc is an official GNU project it is supposed to
follow the GNU coding standards (Debian package gnu-standards).
There you can read

     This option should direct the program to print information about
     its name, version, origin and legal status, all on standard
     output, and then exit successfully.  Other options and arguments
     should be ignored once this is seen, and the program should not
     perform its normal function.

     The first line is meant to be easy for a program to parse; the
     version number proper starts after the last space.  In addition,
     it contains the canonical name for this program, in this format:

          GNU Emacs 19.30

     The program's name should be a constant string; _don't_ compute it
     from `argv[0]'.  The idea is to state the standard or canonical
     name for the program, not its file name.  There are other ways to
     find out the precise file name where a command is found in `PATH'.

     If the program is a subsidiary part of a larger package, mention
     the package name in parentheses, like this:

          emacsserver (GNU Emacs) 19.30


But again, this is of course only valid for the original
GNU-project version.


Attachment: pgp8lnXkvv8TY.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]