On 2005-05-21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew - Supernews <andrew+nonews@supernews.com> writes:
>> On 2005-05-21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> initdb does not use libpq ... it might link to it,
>
>> Linking to it is enough to bring in libc_r, and pick up libc_r's versions
>> of at least some system calls. The ktrace results show this.
>
> [ shrug... ] If libc_r behaves differently than libc in an app that
> doesn't create multiple threads, I think that's an issue to be taking up
> with the libc developers not us.
Further investigation (not yet complete) suggests that this is a link order
dependency problem. It kicks in because libpq is being linked explicitly
with -lc_r (which should not be necessary or desirable), causing libc and
libc_r to be linked in the wrong order if the executable is _not_ linked
with -pthread.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
