[Top][All Lists]

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

Re: proposal - command-line option checking

From: Steven G. Johnson
Subject: Re: proposal - command-line option checking
Date: Thu, 14 Dec 2006 14:37:47 -0500
User-agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)

Bob Friesenhahn wrote:
The reason why Autoconf behaves this way is that it is supposed to be possible to extract several different independently-maintained projects in a directory and drive them all via top configure script. The sub-projects might not use the same version of Autoconf and will surely accept different configuration options. A package maintainer may not know that his package is built subordinate to some other developer's package.

This approach was historically used for the GNU tool set.

This behavior is not broken by my proposal.

As I explained, the argument checking would be disabled for AC_CONFIG_SUBDIRS. I should have also said that AC_CONFIG_SUBDIRS would pass --disable-option-checking to recursive configure invocations, so that they also don't check their options.

My proposal is simply that the options be checked in the common case where only a single configure script is being invoked.


reply via email to

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