https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: mail-mta/sendmail-8.17.1 fails to compile. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html If you think this is a GCC-11 related issue, please block bug 732706.
Created attachment 733969 [details] build.log build log and emerge --info
Possible context of error(s): conf.c:5956:6: error: invalid preprocessing directive #ERROR
The error messege contains this too: "5956 | # ERROR "Berkeley DB file locking needs flock() for version 5.x (and greater?)"
Setting HASFLOCK as mentioned in the 8.17.1 RELEASE_NOTES solves the issue: --- /usr/portage/mail-mta/sendmail/sendmail-8.17.1.ebuild 2021-08-18 22:09:51.000000000 +0200 +++ /usr/local/portage/mail-mta/sendmail/sendmail-8.17.1.ebuild 2021-08-23 12:15:38.725684640 +0200 @@ -52,7 +52,7 @@ eapply_user local confCCOPTS="${CFLAGS}" - local confENVDEF="-DMAXDAEMONS=64 -DHAS_GETHOSTBYNAME2=1" + local confENVDEF="-DMAXDAEMONS=64 -DHAS_GETHOSTBYNAME2=1 -DHASFLOCK=1" local confLDOPTS="${LDFLAGS}" local confLIBS= local confMAPDEF="-DMAP_REGEX" From the release notes: 8.17.1/8.17.1 2021/08/17 [...] Portability: [...] NOTE: File locking using fcntl() does not interoperate with Berkeley DB 5.x (and probably later). Use CDB, flock() (-DHASFLOCK), or an earlier Berkeley DB version. Problem noted by Harald Hannelius.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=893b4643b0d6072be646db7822e15adbea7475bc commit 893b4643b0d6072be646db7822e15adbea7475bc Author: Sam James <sam@gentoo.org> AuthorDate: 2021-08-28 02:28:52 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-08-28 02:29:03 +0000 mail-mta/sendmail: fix build with berkdb Closes: https://bugs.gentoo.org/808954 Thanks-to: Michael Weiser <michael@weiser.dinsnail.net> Signed-off-by: Sam James <sam@gentoo.org> .../sendmail/{sendmail-8.17.1.ebuild => sendmail-8.17.1-r1.ebuild} | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
*** Bug 810742 has been marked as a duplicate of this bug. ***