| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: configure openldap crash warning |
| Date: | 2022-05-09 12:36:47 |
| Message-ID: | 6f2a7259-812f-fc43-494b-22c85cc1490f@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04.05.22 17:16, Tom Lane wrote:
> Hmm, I just tried it with up-to-date MacPorts, and it was a*complete*
> fail: I got all the deprecation warnings (so the system include headers
> were used), and both postgres and libpq.dylib still ended up linked
> against /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP.
Btw., I was a bit puzzled about all this talk about deprecation
warnings, which I have not seen. I turns out that you only get those if
you use the OS compiler, not a third-party gcc installation.
So in terms of my original message, my installation is clearly niche.
The possibly false-positive configure warning is a drop in the bucket
compared to the deprecation warnings from the compiler. So it's
probably okay to leave this as is and encourage users to use openldap.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-05-09 13:06:59 | Re: wrong fds used for refilenodes after pg_upgrade relfilenode changes Reply-To: |
| Previous Message | Peter Eisentraut | 2022-05-09 12:28:13 | Re: configure openldap crash warning |