The following reply was made to PR os-bsdi/2196; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Apache bugs database <[EMAIL PROTECTED]> Cc: Subject: Re: os-bsdi/2196: do not #include <signal.h> (fwd) Date: Thu, 7 May 1998 11:14:33 -0600 (MDT) ---------- Forwarded message ---------- Date: Thu, 07 May 1998 09:19:54 -0700 From: Jon Drukman <[EMAIL PROTECTED]> To: Marc Slemko <[EMAIL PROTECTED]> Subject: Re: os-bsdi/2196: do not #include <signal.h> Marc Slemko wrote: > > On 6 May 1998, Jon Drukman wrote: > > > BSDI BSD/OS 2.1 > > gcc version 2.7.2 > > >Description: > > in include/conf.h and modules/standard/mod_rewrite.h you are including > > <signal.h>. > > this causes a declaration conflict for sys_siglist, which is also provided > > in > > unistd.h. > > >Fix: > > i commented out #include <signal.h> in include/conf.h and > > modules/standard/mod_rewrite.h but i bet you guys can figure out how > > to make it not get in those files in the first place. :) > > Erm... is that the gcc that came with your system or did you install it > yourself? afaik it's the one that came with the system. > Does compiling the following program: > > -------- > #include <signal.h> > #include <unistd.h> > > int main () { } > -------- > > give the same error? yes. erehwon [2] gcc test.c In file included from test.c:2: /usr/local/lib/gcc-lib/i386-unknown-bsdi2.0.1/2.7.2/include/unistd.h:143: conflicting types for `sys_siglist' /usr/include/signal.h:50: previous declaration of `sys_siglist' > If so, that isn't anything wrong with Apache but something broken with > your header files. I really don't think that BSD/OS is broken like that > and Apache has been including both for a long time. hrm. wacky. we've been using this gcc with apache since 1.0... well i'll see about upgrading gcc. thanks -- Jon Drukman [EMAIL PROTECTED] ----------------------------------------------------------------------- Plan: Eat right, exercise regularly, die anyway.