Jon Ringle
2009-Jul-16 23:00 UTC
[klibc] [PATCH] fix warning include/signal.h:47:5: warning: "SIGRTMAX" is not defined
--- usr/include/signal.h | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/usr/include/signal.h b/usr/include/signal.h index a513282..4ed65bc 100644 --- a/usr/include/signal.h +++ b/usr/include/signal.h @@ -44,10 +44,12 @@ typedef int sig_atomic_t; /* The kernel header files are inconsistent whether or not SIGRTMAX is inclusive or exclusive. POSIX seems to state that it's inclusive, however. */ +#ifdef SIGRTMAX #if SIGRTMAX >= _NSIG # undef SIGRTMAX # define SIGRTMAX (_NSIG-1) #endif +#endif __extern const char *const sys_siglist[_NSIG]; __extern const char *const sys_sigabbrev[_NSIG];
H. Peter Anvin
2009-Aug-09 22:29 UTC
[klibc] [PATCH] fix warning include/signal.h:47:5: warning: "SIGRTMAX" is not defined
On 07/16/2009 04:00 PM, Jon Ringle wrote:> --- > usr/include/signal.h | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/usr/include/signal.h b/usr/include/signal.h > index a513282..4ed65bc 100644 > --- a/usr/include/signal.h > +++ b/usr/include/signal.h > @@ -44,10 +44,12 @@ typedef int sig_atomic_t; > /* The kernel header files are inconsistent whether or not > SIGRTMAX is inclusive or exclusive. POSIX seems to state that > it's inclusive, however. */ > +#ifdef SIGRTMAX > #if SIGRTMAX >= _NSIG > # undef SIGRTMAX > # define SIGRTMAX (_NSIG-1) > #endif > +#endif >This is a much bigger problem... if SIGRTMAX is undefined then we are using signal numbers blind. What configuration is this on? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.