Date: Sat, 25 Nov 2023 16:41:49 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 275328] <signal.h> fails to expose SA_* macros without XSI Message-ID: <bug-275328-99-ycVbMonDK8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275328-99@https.bugs.freebsd.org/bugzilla/> References: <bug-275328-99@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=3D275328 Warner Losh <imp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org Assignee|standards@FreeBSD.org |imp@FreeBSD.org Status|New |Open --- Comment #1 from Warner Losh <imp@FreeBSD.org> --- diff --git a/sys/sys/signal.h b/sys/sys/signal.h index 0ab2a205a92c..8f3a0dec8fee 100644 --- a/sys/sys/signal.h +++ b/sys/sys/signal.h @@ -391,7 +391,7 @@ struct sigaction { #define SA_NOCLDSTOP 0x0008 /* do not generate SIGCHLD on child stop */ #endif /* __POSIX_VISIBLE || __XSI_VISIBLE */ -#if __XSI_VISIBLE +#if __XSI_VISIBLE || __POSIX_VISIBLE >=3D 200809 #define SA_ONSTACK 0x0001 /* take signal on signal stack */ #define SA_RESTART 0x0002 /* restart system call on signal re= turn */ #define SA_RESETHAND 0x0004 /* reset to SIG_DFL when taking sig= nal */ Appears to be the ask. It seems reasonable. I'll note that there's a number= of alignment issues with the standards that we have (usually erring on the sid= e of defining too much). A large part of the reason for this is that while POSIX.1-2008 (aka Issue 7) and (to a lessor degree) POSIX.1-2001 (issue 6) = are basically available, earlier versions are not, so it is kinda hard to retrospectively get all the fiddly details right. other implementations also are sloppy in this regard towards earlier standards, leading to the mistaken impression that symbols are available earlier than they really are (note: n= ote the case here, this bug is spot on). Unless I see an objection soonish, I'll commit and merge this in the coming weeks. Is there a specific port for this that prompted this test/bug? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275328-99-ycVbMonDK8>