Re: [patch] build issues on Win32

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dag-Erling Smørgrav <des(at)des(dot)no>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [patch] build issues on Win32
Date: 2010-03-10 16:17:11
Message-ID: 16449.1268237831@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des(at)des(dot)no> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> "Dag-Erling Smrgrav" <des(at)des(dot)no> writes:
>>> 1. PostgreSQL's private versions of inet_aton etc. can conflict with
>>> similar functions in other libraries (in my case, PostgreSQL's
>>> inet_aton conflicts with libavformat's).

>> So what? We don't link with those libraries.

> Your users might need to link with both.

We don't support linking the backend into other applications. If you're
complaining about libpq, the right thing for that is to use a platform
that can suppress non-exported symbols from a shared library. Maybe
what we need to do is teach the mingw build path how to respect the
exports list for libpq?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dag-Erling Smørgrav 2010-03-10 16:37:55 Re: [patch] build issues on Win32
Previous Message Magnus Hagander 2010-03-10 16:07:12 Re: [patch] build issues on Win32