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

From Bruce Momjian
Subject Re: Have configure complain about unknown options
Date
Msg-id 200605091535.k49FZWj18959@candle.pha.pa.us
Whole thread Raw
In response to Re: Have configure complain about unknown options  ("Marko Kreen" <markokr@gmail.com>)
Responses Re: Have configure complain about unknown options  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-patches
Marko Kreen wrote:
> On 5/9/06, Peter Eisentraut <peter_e@gmx.net> wrote:
> > Am Freitag, 5. Mai 2006 20:07 schrieb Martijn van Oosterhout:
> > > 1. Provide an escape option they can add
> > > 2. Package systems can usually apply patches prior to compiling, they can
> > > always remove the offending line if they like.
> > > 3. Try and get feedback from them now rather than wait
> >
> > My feedback is this: You are going to enter a world of pain.
>
> Seems that way.  Especially if the non-PGAC options won't be
> handled automatically.
>
> Some projects have solved the problem different way - by printing
> out the summary of most important options at the end of configure:
>
> PostgreSQL version X.X.X
> OpenSSL: no
> Integer datatime: yes
> Python: yes
> Perl: yes
>
> So at the end of configure the user can visually confirm
> his expectations without needing to parse the noise
> from full configure output.  Maybe this would be better
> solution.

Seems we would be best printing out options we _didn't_ undertand at the
end of the build.

--
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-patches by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Cleaning up multiply-defined-symbol warnings on OS X
Next
From: Tom Lane
Date:
Subject: Re: Encryption of .pgpass