Re: initdb fails on ultra2 sparc64, freebsd 5.4

From: Andrew - Supernews <andrew+nonews(at)supernews(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: initdb fails on ultra2 sparc64, freebsd 5.4
Date: 2005-05-23 08:18:07
Message-ID: slrnd934dv.1feb.andrew+nonews@trinity.supernews.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2005-05-21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew - Supernews <andrew+nonews(at)supernews(dot)com> writes:
>> On 2005-05-21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Julien Vallet 2005-05-23 11:49:12 BUG #1677: Bug in select with Union
Previous Message Mark Shewmaker 2005-05-22 23:12:27 Re: pg_dump table ordering bug [8.0.1]