Message-ID: <a3a4ab66-7f94-ea6d-0de2-565828a769ce@enterprisedb.com>
Date: Mon, 9 May 2022 14:28:13 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.9.0
Subject: Re: configure openldap crash warning
Content-Language: en-US
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
References: <fedacd7c-2a38-25c9-e7ff-dea549d0e979@enterprisedb.com>
 <1832824.1651500238@sss.pgh.pa.us>
 <f2393be8-2b92-1ee6-0812-324cf7660f24@enterprisedb.com>
 <2358598.1651677372@sss.pgh.pa.us> <2360302.1651678212@sss.pgh.pa.us>
 <2957308.1651860043@sss.pgh.pa.us> <2971088.1651865107@sss.pgh.pa.us>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <2971088.1651865107@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a3a4ab66-7f94-ea6d-0de2-565828a769ce%40enterprisedb.com>
Precedence: bulk

On 06.05.22 21:25, Tom Lane wrote:
> I wrote:
>> After thinking about this for awhile, it seems like the best solution
>> is to make configure proceed like this:
> 
>> 1. Find libldap.
>> 2. Detect whether it's OpenLDAP 2.5 or newer.
>> 3. If not, try to find libldap_r.
> 
> Here's a proposed patch for that.  It seems to do the right thing
> with openldap 2.4.x and 2.6.x, but I don't have a 2.5 installation
> at hand to try.

This patch works for me.  I think it's a good solution.