maintainer-feedback requested: [Bug 264978] graphics/wayland: MSG_CMSG_CLOEXEC is broken

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 01 Jul 2022 15:28:42 UTC
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-x11 (Nobody)
<x11@FreeBSD.org> for maintainer-feedback:
Bug 264978: graphics/wayland: MSG_CMSG_CLOEXEC is broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264978



--- Description ---
Trying to build graphics/wayland on poudriere FreeBSD-13 / amd64, it fails with
the following error:

[  7% 7/88] cc -Isrc/libwayland-private.a.p -Isrc -I../src
-I/usr/local/include/libepoll-shim -I/usr/local/include -fno-color-diagnostics
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -O3 -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -fvisibility=hidden -O2 -pipe
-fstack-protector-strong -fno-strict-aliasing -fPIC -MD -MQ
src/libwayland-private.a.p/wayland-os.c.o -MF
src/libwayland-private.a.p/wayland-os.c.o.d -o
src/libwayland-private.a.p/wayland-os.c.o -c ../src/wayland-os.c
FAILED: src/libwayland-private.a.p/wayland-os.c.o 
cc -Isrc/libwayland-private.a.p -Isrc -I../src
-I/usr/local/include/libepoll-shim -I/usr/local/include -fno-color-diagnostics
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -O3 -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -fvisibility=hidden -O2 -pipe
-fstack-protector-strong -fno-strict-aliasing -fPIC -MD -MQ
src/libwayland-private.a.p/wayland-os.c.o -MF
src/libwayland-private.a.p/wayland-os.c.o.d -o
src/libwayland-private.a.p/wayland-os.c.o -c ../src/wayland-os.c
../src/wayland-os.c:90:25: error: use of undeclared identifier 'SOL_LOCAL'
	if (getsockopt(sockfd, SOL_LOCAL, LOCAL_PEERCRED, &ucred, &len) < 0 ||
			       ^
../src/wayland-os.c:178:9: warning: Using fallback directly since
MSG_CMSG_CLOEXEC is broken. [-W#pragma-messages]
#pragma message("Using fallback directly since MSG_CMSG_CLOEXEC is broken.")
	^
1 warning and 1 error generated.
ninja: build stopped: subcommand failed.

Previously, during configure, there is this message:

Checking if "MSG_CMSG_CLOEXEC works correctly" compiles: NO

Any idea of a possible cause?