Re: [COMMITTERS] pgsql: Make S_IRGRP etc available in mingw builds as well as MSVC.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Make S_IRGRP etc available in mingw builds as well as MSVC.
Date: 2010-12-12 18:54:18
Message-ID: 7407.1292180058@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 12/12/2010 01:43 PM, Tom Lane wrote:
>> (Hm, I wonder whether BCC defines them either...)

> Is anyone building the client stuff with BCC any more? I don't recall
> having heard of anyone doing so for quite some years.

It's a fair question. We could clean up some of these messy ifdefs
if we dropped support for that combination. I assume that an MSVC-built
libpq.dll would still work for Borland users, no?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2010-12-12 19:07:30 Re: [COMMITTERS] pgsql: Make S_IRGRP etc available in mingw builds as well as MSVC.
Previous Message Andrew Dunstan 2010-12-12 18:47:52 Re: [COMMITTERS] pgsql: Make S_IRGRP etc available in mingw builds as well as MSVC.

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-12-12 19:07:30 Re: [COMMITTERS] pgsql: Make S_IRGRP etc available in mingw builds as well as MSVC.
Previous Message Andrew Dunstan 2010-12-12 18:47:52 Re: [COMMITTERS] pgsql: Make S_IRGRP etc available in mingw builds as well as MSVC.