Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 79275B5DBC6 for ; Sat, 2 Jul 2011 22:51:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 21907-07 for ; Sun, 3 Jul 2011 01:51:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 3EB7AB5DBC1 for ; Sat, 2 Jul 2011 22:51:27 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p631onLU025176; Sat, 2 Jul 2011 21:50:49 -0400 (EDT) To: Dave Pooser cc: pgsql-admin@postgresql.org Subject: Re: Help compiling --with-ldap on Solaris 11 Express? In-reply-to: References: Comments: In-reply-to Dave Pooser message dated "Sat, 02 Jul 2011 20:02:17 -0500" Date: Sat, 02 Jul 2011 21:50:49 -0400 Message-ID: <25175.1309657849@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201107/17 X-Sequence-Number: 37796 Dave Pooser writes: > It seems there's some magic incantation to REALLY bind that I'm just not > seeing here. Any help gratefully accepted. Well, I don't know anything about Solaris either, but this bit looks suspicious: > root@testdb:/home/locadmin/postgresql-9.0.4# ldd > /usr/local/pgsql/bin/postgres > ... > libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 > libldap.so.5 => /usr/lib/libldap.so.5 > ... I gather from a bit of googling that the internal data structures are different between libldap and libldap_r, which means you really really don't want both versions getting bound into one executable. Most likely what is happening is that one of the other libraries called by the postmaster is pulling in libldap_r --- a bit of research with ldd should confirm or deny that. If so, you could probably fix things by hacking LDAP_LIBS_BE in the configured src/Makefile.global to pull in libldap_r not libldap. If you've got different libraries calling both versions, then some library recompilation is going to be needed :-( regards, tom lane