Re: configure openldap crash warning
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-05-04T15:30:12Z
Lists: pgsql-hackers
I wrote: > Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes: >> I tried building with Homebrew-supplied openldap. What ends up >> happening is that the postgres binary is indeed linked with openldap, >> but libpq still is linked against the OS-supplied LDAP framework. >> (Checked with "otool -L" in each case.) Can someone else reproduce >> this, too? > [ it works with MacPorts ] Oh, I have a theory about this: I bet your Homebrew installation has a recent OpenLDAP version that only supplies libldap not libldap_r. In that case, configure will still find libldap_r available and will bind libpq to it, and you get the observed result. The configure check is not sophisticated enough to realize that it's finding chunks of two different OpenLDAP installations. Not sure about a good fix. If we had a way to detect which library file AC_CHECK_LIB finds, we could verify that libldap and libldap_r come from the same directory ... but I don't think we have that. regards, tom lane
Commits
-
configure: don't probe for libldap_r if libldap is 2.5 or newer.
- c61f36d99606 10.22 landed
- aff45c879e01 15.0 landed
- af9b96767153 13.8 landed
- 8ed13fb9346d 12.12 landed
- 36d76da8156a 11.17 landed
- 12736e7dc326 14.4 landed