Enabling use of fetch(3) -- a perfectly sensible thing to do (why is it not on by default?) -- fails on systems built WITHOUT_KERBEROS. Because upstream configure unconditionally adds -lcom_err together with -lfetch. But libcom_err.{a,so} are only available, if the world is built with Kerberos enabled. This causes configure-script to fail... A brutal hack would simply remove all mentions of -lcom_err from ${WRKSRC}/configure at the post-patch time -- using ${REINPLACE_CMD}. Something better may be required for upstream acceptance...
This was fixed by OpenLDAP ITS #8874.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=7988695148ca15fb1e8aa498b032d4facf1cf05e commit 7988695148ca15fb1e8aa498b032d4facf1cf05e Author: Xin LI <delphij@FreeBSD.org> AuthorDate: 2021-10-24 07:47:14 +0000 Commit: Xin LI <delphij@FreeBSD.org> CommitDate: 2021-10-24 07:53:09 +0000 net/openldap2[45]-server: Fix build on systems WITHOUT_KERBEROS when FETCH is on. PR: ports/259345 Reported by: mi net/openldap24-server/Makefile | 7 ++++--- net/openldap24-server/files/patch-ITS8874 (new) | 20 ++++++++++++++++++++ net/openldap25-server/Makefile | 11 ++++++++--- net/openldap25-server/files/patch-ITS8874 (new) | 20 ++++++++++++++++++++ 4 files changed, 52 insertions(+), 6 deletions(-)