Date: Mon, 15 Nov 2021 21:23:11 +0000 From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 259787] sched.h: unknown type name 'cpu_set_t' after 160b4b922b6021848b6b48afc894d16b879b7af2 Message-ID: <bug-259787-12827-Zheoh365bT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259787-12827@https.bugs.freebsd.org/bugzilla/> References: <bug-259787-12827@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259787 --- Comment #14 from Jan Beich <jbeich@FreeBSD.org> --- According to base 90fa9705d5cd _WITH_CPU_SET_T is supposed to enable the new functionality. If many ports are broken without it the conditional is point= less and all regressions should be fixed the hard way (a la Clang upgrades). AC_CHECK_FUNC(sched_getaffinity) from autotools and meson.get_compiler('c').has_function('sched_getaffinity') test symbol visibility without using #include <sched.h>. Such behavior is allowed in C unlike C++ but often warned via -Wimplicit-function-declaration. For exampl= e, GNU libc hides extensions like sched_getaffinity by default. However, NetBSD added sched_getaffinity_np in 2008-10-31 and DragonFly added sched_getaffin= ity in 2017-01-14, both following the BSD convention of exposing all extensions unless standard conformance (e.g., _POSIX_C_SOURCE) is requested. https://www.man7.org/linux/man-pages/man2/sched_getaffinity.2.html https://man.dragonflybsd.org/?command=3Dsched_getaffinity§ion=3D2 https://man.netbsd.org/sched_getaffinity_np.3 After FreeBSD finally got rid of _WITH_GETLINE and _WITH_DPRINTF we now have _WITH_CPU_SET_T to deal with. It's as ugly as cheating _POSIX_C_SOURCE by defining __BSD_VISIBLE. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259787-12827-Zheoh365bT>