Tom Lane wrote:
> 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.

+1 from here as well, if that wasn' obvious :-)

(will get back to the actual issues at hand when I get back in a more 
connected mode in a couple of days, unless they are already solved by then)

//Magnus

In response to

• Re: [COMMITTERS] pgsql: Sigh ... at 2008-05-03 17:17:34 from Tom Lane

pgsql-hackers by date

Next:	From: Andrew Dunstan	Date: 2008-05-03 23:35:37
	Subject: Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Previous:	From: Joshua D. Drake	Date: 2008-05-03 17:31:01
	Subject: Re: statement timeout vs dump/restore

pgsql-committers by date

Next:	From: User Jbcooley	Date: 2008-05-03 20:32:43
	Subject: npgsql - Npgsql: Allow IOException in listen thread to be handled by
Previous:	From: User H-saito	Date: 2008-05-03 18:52:06
	Subject: psqlodbc - psqlodbc: Adjustment of a library.

pgsql-patches by date

Next:	From: Dave Page	Date: 2008-05-03 19:44:56
	Subject: Re: Exposing keywords to clients
Previous:	From: Andreas 'ads' Scherbaum	Date: 2008-05-03 19:12:51
	Subject: Re: create or replace language