Date: Mon, 20 Dec 2021 20:05:38 +0000 From: bugzilla-noreply@freebsd.org To: desktop@FreeBSD.org Subject: [Bug 259787] sched.h: unknown type name 'cpu_set_t' after 160b4b922b6021848b6b48afc894d16b879b7af2 Message-ID: <bug-259787-39348-0rO4GeOTNT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259787-39348@https.bugs.freebsd.org/bugzilla/> References: <bug-259787-39348@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 #37 from Stefan E=C3=9Fer <se@FreeBSD.org> --- (In reply to Gleb Popov from comment #36) Building lang/ghc on -CURRENT works after commit 5e04571cf3cf, which removed the need to specify -D_WITH_CPU_SET_T to make parts of sched.h visible. But I'm not sure whether that part of the commit should not be reverted, si= nce it made some ports assume that they were being built on a Linux system with GLIBC. Some of the CPU_* macros have conflicting signatures on FreeBSD and in GLIB= C, and now some ports need individual patches to make them build. It may be better to just rely on the standard method of passing -D_WITH_CPU_SET_T to enable those macros, than to expect port maintainers to find the individual cure for their ports ... --=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-39348-0rO4GeOTNT>