[Top][All Lists]

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

Re: Confusing/bogus message in config.log

From: Derek R. Price
Subject: Re: Confusing/bogus message in config.log
Date: Thu, 29 Mar 2001 12:05:14 -0500

Tim Van Holder wrote:

> True. But if you apply 'the program being run', then you need a seperate
> version for configure, as it is neither autoconf, nor the package,
> really.
> I guess that is what it boils down to: do we see 'configure' as a) a
> program in its own right, b) an inextricable part of a package, or
> c) part of autoconf (though included with many other packages).
> I suppose b) seems the most logical choice.
> So the shortest thing that has all the info and is compliant, would
> probably be
>         GNU configure 2.50, for CVS 1.11.1
> With the one drawback that it more clearly suggests 2.50 is configure's
> version number.

Unfortunately this diverges from the GNU coding standard ( ).  Succintly put, it says
the output should be like:


where PACKAGE_VERSION is included only when != PROGRAMRUNNING_VERSION and
(PACKAGE .*) is only included when != PROGRAMRUNNING.

I think we're debating this only because RMS doesn't seem to have left much
room for generated programs and we seem to agree that it would be useful to
know the version of Autoconf which generated a configure script as well as
the package it came from without having to track down and ask a user
reporting a bug what version they were running when they already sent the
output of 'configure --version'.


Derek Price                      CVS Solutions Architect ( )
mailto:address@hidden         CollabNet ( )
All those who believe in psychokinesis raise my hand.

reply via email to

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