From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: configure openldap crash warning
Date: Wed, 4 May 2022 16:05:45 +0200
Message-ID: <f2393be8-2b92-1ee6-0812-324cf7660f24@enterprisedb.com> (raw)
In-Reply-To: <1832824.1651500238@sss.pgh.pa.us>
References: <fedacd7c-2a38-25c9-e7ff-dea549d0e979@enterprisedb.com>
<1832824.1651500238@sss.pgh.pa.us>
On 02.05.22 16:03, Tom Lane wrote:
> I'm not that excited about getting rid of this warning, because to the
> extent that anyone notices it at all, it'll motivate them to get OpenLDAP
> from Homebrew or MacPorts, which seems like a good thing.
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, tgl@sss.pgh.pa.us
Subject: Re: configure openldap crash warning
In-Reply-To: <f2393be8-2b92-1ee6-0812-324cf7660f24@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox