Re: [PATCH] Have configure complain about unknown options - Mailing list pgsql-patches

From Dave Page
Subject Re: [PATCH] Have configure complain about unknown options
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E401387F15@ratbert.vale-housing.co.uk
Whole thread Raw
In response to [PATCH] Have configure complain about unknown options  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: [PATCH] Have configure complain about unknown options  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches

> -----Original Message-----
> From: pgsql-patches-owner@postgresql.org
> [mailto:pgsql-patches-owner@postgresql.org] 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 be better to give explicit errors for
> unknown options.
>

I'm not in a position to argue about why autoconf works this way, but I
can say that I'd like to see unsupported options rejected if there is a
sensible way to do it. I've been bitten more than once by mistakenly
using --enable-foo rather than --with-foo, or just plain mis-typing.

Regards, Dave.

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #2401: spinlocks not available on amd64
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCH] Have configure complain about unknown options