Libpq problem on Windows. - Mailing list pgsql-hackers

From Dave Page
Subject Libpq problem on Windows.
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E430682C@ratbert.vale-housing.co.uk
Whole thread Raw
List pgsql-hackers
I posted a message to pgsql-hackers-win32 regarding a problem with libpq
exports on Win32 the other day, but have yet to receive any replies.
Magnus & I have discussed the problem over IM and we both believe it is
important to fix, but neither of us are fluent enough in make-ese to do
so.

Basically the issue is that the symbols exported by the mingw build of
libpq.dll do not match those exported by the VC++/Borland builds. What
we seem to get is:

- Mingw exports *all* symbols appropiate for the given build.
- VC++/Borland builds appear to export only the published API, but not
the SSL related symbols (even with SSL enabled in the build).

I can probably sort the second problem by adding a second set of .def
files for SSL builds, however it seems to me that the mingw build should
not export all symbols. Whether or nt that is changed, the 2 build types
certainly need to be brought into sync otherwise Windows users may end
up seeing unexplained crashes.

Any comments on what should be done (and whether I should hack the
BCC/VC++ stuff)?

Regards, Dave.


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Bug in Beta3 with parser?
Next
From: "Serguei A. Mokhov"
Date:
Subject: Re: pg_upgrade project: high-level design proposal of