2010/3/11 Dag-Erling Smørgrav <d...@des.no>: > Greg Stark <gsst...@mit.edu> writes: >> I would be sad about this. It seems likely there are platforms where >> it's important. But I'm not really about to spend the effort to fix it >> up myself and I agree it wouldn't be worth hacking the source to get >> it to work. I'm a bit puzzled why the symbol conflicts occur only with >> static linking though -- it seems like static linking would give more >> opportunity to isolate symbols than dynamic linking, not less. Perhaps >> our static linking rules are broken? > > A dynamic library is a single entity with a certain degree of isolation. > You can hide symbols so they are only visible within that library.
In particular, libpq only exports a fixed subset of symbols on any platform that supports that (which includes Windows). AFAIK, there is no way to make that restriction on static libraries, at least not on Windows. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
