From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Dag-Erling Smørgrav <des(at)des(dot)no> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] build issues on Win32 |
Date: | 2010-03-11 17:58:51 |
Message-ID: | 9837222c1003110958q25a67d2bv306cfddc0aeac9ff@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/3/11 Dag-Erling Smørgrav <des(at)des(dot)no>:
> Greg Stark <gsstark(at)mit(dot)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/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-03-11 18:32:19 | Re: [patch] build issues on Win32 |
Previous Message | Pavel Stehule | 2010-03-11 17:34:24 | Re: tsearch profiling - czech environment - take 55MB |