Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mIu2I-0000Ba-9e for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Aug 2021 14:37:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mIu2H-0002xe-6A for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Aug 2021 14:37:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mIu2G-0002xJ-VO for pgsql-bugs@lists.postgresql.org; Wed, 25 Aug 2021 14:37:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mIu2E-0003y5-UK for pgsql-bugs@lists.postgresql.org; Wed, 25 Aug 2021 14:37:47 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 17PEae9U545974; Wed, 25 Aug 2021 10:36:40 -0400 From: Tom Lane To: =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= cc: pgsql-bugs@lists.postgresql.org Subject: Re: No libldap_r in OpenLDAP 2.5 - use LDAP_API_FEATURE_X_OPENLDAP_REENTRANT from ldap_features.h In-reply-to: <8bf71cb05679342f8a09206cb03fc727d5d52830.camel@aegee.org> References: <20210825052142.Horde.fX47Irhz5YmXoRVbIbyYUJm@webmail.aegee.org> <520273.1629872978@sss.pgh.pa.us> <3894d2a91d141b0fe454da01b3b7faad6fa9d07a.camel@aegee.org> <544882.1629900910@sss.pgh.pa.us> <8bf71cb05679342f8a09206cb03fc727d5d52830.camel@aegee.org> Comments: In-reply-to =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= message dated "Wed, 25 Aug 2021 17:27:26 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <545972.1629902200.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Aug 2021 10:36:40 -0400 Message-ID: <545973.1629902200@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =3D?UTF-8?Q?=3DD0=3D94=3DD0=3DB8=3DD0=3DBB=3DD1=3D8F=3DD0=3DBD_?=3D =3D?UT= F-8?Q?=3DD0=3D9F=3DD0=3DB0=3DD0=3DBB=3DD0=3DB0=3DD1=3D83=3DD0=3DB7=3DD0=3D= BE=3DD0=3DB2?=3D writes: > I run Linux from Scratch system. All old binaries, are linked with > libldap(_r)-2.4, all new things get linked towards libldap-2.5 . So > the configuration step always sees libldap-2.5 as most current (and its > header files). I can in theory point the build process to versioned- > headers, but I do not have to. > The problem here is, that libldap_r-2.4, libldap-2.4, and libldap-2.5 > are installed on the system. I want that libpq.so is not linked with > libldap_r-2.4, but with libldap-2.5. If that is your plan, then you should have only the 2.5 libldap-devel support installed, not 2.4. In particular, that would mean that you shouldn't have any .so symlinks for the 2.4 libraries, which should cause configure not to see them. regards, tom lane