| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Adrian Ho <ml+postgresql(at)03s(dot)net>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17083: [PATCH] PostgreSQL fails to build with OpenLDAP 2.5.x |
| Date: | 2021-07-10 14:50:29 |
| Message-ID: | 2377740.1625928629@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Fri, Jul 09, 2021 at 12:40:16PM -0400, Tom Lane wrote:
>> Done that way.
> This broke LDAPS, and the regression tests of src/test/ldap/. Elver
> is one animal complaining, but I am able to reproduce this failure on
> my own Debian laptop:
Oh, that's interesting. elver's failure seems to be because it's now
deciding it doesn't HAVE_LDAP_INITIALIZE. However, on my RHEL8 machine
the current configure coding is still finding ldap_initialize; so I'd
assumed this was something BSD-specific. If you're seeing it on Debian
then I'm really confused about what the problem is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-07-10 17:25:33 | Re: BUG #17083: [PATCH] PostgreSQL fails to build with OpenLDAP 2.5.x |
| Previous Message | Michael Paquier | 2021-07-10 11:56:17 | Re: BUG #17083: [PATCH] PostgreSQL fails to build with OpenLDAP 2.5.x |