Re: ./configure argument checking

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: ./configure argument checking
Date: 2006-10-13 18:55:42
Message-ID: 20061013185541.GL28647@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 13, 2006 at 08:40:42PM +0200, Peter Eisentraut wrote:
> Tom Lane wrote:
> > Not sure what to do about that --- I doubt that raising this warning
> > to error would be a good idea, seeing how firmly the upstream
> > developers believe it shouldn't even be a warning. Is there any sort
> > of "quiet mode" possible that would report only warnings? Would it
> > be a good idea if it were possible?
>
> peter(at)colt:~/devel/pg82/pgsql$ ./configure --enable-foo --quiet
> *** Option ignored: --enable-foo
> peter(at)colt:~/devel/pg82/pgsql$

Odd, I can't get that on a very recent checkout of HEAD:
decibel(at)phonebook(dot)1[13:51]~/pgsql/HEAD:156%./configure
--with-includes=/opt/local/include --with-libraries=/opt/local/lib
--with-pgport=5820 --enable-depend
--prefix=/Users/decibel/pgsql/HEAD/820 --with-blarg --enable-blarg |
grep blarg
decibel(at)phonebook(dot)1[13:54]~/pgsql/HEAD:157%
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-10-13 19:07:50 Re: index advisor
Previous Message Kai-Uwe Sattler 2006-10-13 18:49:05 index advisor