Skip site navigation (1) Skip section navigation (2)

Re: Have configure complain about unknown options

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: pgsql-patches(at)postgresql(dot)org, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Have configure complain about unknown options
Date: 2006-05-09 08:53:23
Message-ID: (view raw or whole thread)
Lists: pgsql-patches
On 5/9/06, Peter Eisentraut <peter_e(at)gmx(dot)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


In response to


pgsql-patches by date

Next:From: Martijn van OosterhoutDate: 2006-05-09 08:55:55
Subject: Re: Have configure complain about unknown options
Previous:From: Martijn van OosterhoutDate: 2006-05-09 08:41:38
Subject: Re: Cleaning up multiply-defined-symbol warnings on OS X

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group