From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Sigh ... |
Date: | 2008-05-03 17:17:34 |
Message-ID: | 9771.1209835054@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Peter Eisentraut wrote:
>> Btw., it is quite easily possible to use the autom4te tracing facility to
>> parse the configure.ac file, in case you are interested in generating some of
>> the Windows build code automatically.
> Yeah, maybe. Let's fix the issue pg_config.h.win32 that Tom raised first.
+1 for both. We really need to eliminate as much redundancy as we can
between the two build systems, because it'll keep biting us until we do.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | User H-saito | 2008-05-03 18:52:06 | psqlodbc - psqlodbc: Adjustment of a library. |
Previous Message | User Fxjr | 2008-05-03 15:33:19 | npgsql - Npgsql2: Added a prepared bytea support test. |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-05-03 17:31:01 | Re: statement timeout vs dump/restore |
Previous Message | Tom Lane | 2008-05-03 17:01:36 | Re: statement timeout vs dump/restore |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas 'ads' Scherbaum | 2008-05-03 17:26:12 | Re: configure option for XLOG_BLCKSZ |
Previous Message | Tom Lane | 2008-05-03 17:14:35 | Re: configure option for XLOG_BLCKSZ |