| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, 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 20:13:21 |
| Message-ID: | 20061013201321.GP1896@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 13, 2006 at 01:24:52PM -0400, Tom Lane wrote:
> "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.
At the end of the day configure is just a shell script, so worst case
you load all the warnings into an environment variable and print that
at the end...
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-10-13 20:14:43 | Re: more anti-postgresql FUD |
| Previous Message | Jim C. Nasby | 2006-10-13 20:01:22 | Re: ./configure argument checking |