Re: ./configure argument checking

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

"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> Hrm... I don't suppose there's a way to capture the critical warnings in
> a temporary file and then cat that at the end? (I'm assuming that it'll
> be nearly impossible to get a quite mode out of autoconf...)

Hmm ... maybe we could just rearrange the script to produce the warnings
at the very end? I'm not sure how much flexibility autoconf gives you
concerning the ordering of end-game processing, but it'd be worth trying.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-10-13 17:30:24 Re: [PERFORM] Hints proposal
Previous Message Jeff Davis 2006-10-13 17:23:31 Re: [PERFORM] Hints proposal