Re: [PATCHES] [PATCH] Have configure complain about unknown options

2006-05-05 Thread Marko Kreen
On 5/4/06, Tom Lane [EMAIL PROTECTED] wrote: Martijn van Oosterhout kleptog@svana.org writes: Currently, configure ignores unknown --enable/disable/with/without options. The autoconf people consider that a feature, not a bug. I'm disinclined to second-guess the designers of the tool,

Re: [PATCHES] [PATCH] Have configure complain about unknown options

2006-05-05 Thread Martijn van Oosterhout
On Fri, May 05, 2006 at 02:22:25PM +0300, Marko Kreen wrote: AFAIK that 'feature' is there to support configuring a 'tree' of projects (like gcc), where subprojects have their own configure scripts with different options. That way you can give all options to top-level configure script which

Re: [PATCHES] [PATCH] Have configure complain about unknown options

2006-05-05 Thread Dave Page
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marko Kreen Sent: 05 May 2006 12:22 To: Tom Lane Cc: Martijn van Oosterhout; pgsql-patches@postgresql.org Subject: Re: [PATCHES] [PATCH] Have configure complain about unknown options

Re: [PATCHES] [PATCH] Have configure complain about unknown options

2006-05-05 Thread Bruce Momjian
PROTECTED] On Behalf Of Marko Kreen Sent: 05 May 2006 12:22 To: Tom Lane Cc: Martijn van Oosterhout; pgsql-patches@postgresql.org Subject: Re: [PATCHES] [PATCH] Have configure complain about unknown options As PostgreSQL tree is not set up that way, I think for clarity sake it would

Re: [PATCHES] [PATCH] Have configure complain about unknown options

2006-05-05 Thread Martijn van Oosterhout
On Fri, May 05, 2006 at 08:34:36AM -0400, Bruce Momjian wrote: I am thinking we would need an option at the start like --strict that would throw an error for any later invalid options. Well, --strict would be tricky, if it's possible. My reading of the autoconf code doesn't indicate a means

[PATCHES] [PATCH] Have configure complain about unknown options

2006-05-04 Thread Martijn van Oosterhout
Currently, configure ignores unknown --enable/disable/with/without options. Personally I find this behaviour annoying, so here is a patch that fixes it. Example: $ ./configure --enable-depends checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu snip

Re: [PATCHES] [PATCH] Have configure complain about unknown options

2006-05-04 Thread Tom Lane
Martijn van Oosterhout kleptog@svana.org writes: Currently, configure ignores unknown --enable/disable/with/without options. The autoconf people consider that a feature, not a bug. I'm disinclined to second-guess the designers of the tool, especially with a patch like this that mucks with the

Re: [PATCHES] [PATCH] Have configure complain about unknown options

2006-05-04 Thread Martijn van Oosterhout
On Thu, May 04, 2006 at 12:51:34PM -0400, Tom Lane wrote: Martijn van Oosterhout kleptog@svana.org writes: Currently, configure ignores unknown --enable/disable/with/without options. The autoconf people consider that a feature, not a bug. I'm disinclined to second-guess the designers of