Received: (qmail 24311 invoked by uid 2012); 6 May 1998 18:48:14 -0000 Message-Id: <19980506184814.24310.qmail@hyperreal.org> Date: 6 May 1998 18:48:14 -0000 From: Jon Drukman Reply-To: jsd@gamespot.com To: apbugs@hyperreal.org Subject: do not #include X-Send-Pr-Version: 3.2 >Number: 2196 >Category: os-bsdi >Synopsis: do not #include >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed May 6 11:50:00 PDT 1998 >Last-Modified: Thu May 7 10:20:01 PDT 1998 >Originator: jsd@gamespot.com >Organization: >Release: 1.3b6 >Environment: BSDI BSD/OS 2.1 gcc version 2.7.2 >Description: in include/conf.h and modules/standard/mod_rewrite.h you are including . this causes a declaration conflict for sys_siglist, which is also provided in unistd.h. >How-To-Repeat: >Fix: i commented out #include 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. :) >Audit-Trail: From: Marc Slemko To: Jon Drukman Cc: apbugs@hyperreal.org Subject: Re: os-bsdi/2196: do not #include Date: Wed, 6 May 1998 23:51:29 -0600 (MDT) 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 > . > this causes a declaration conflict for sys_siglist, which is also provided in > unistd.h. > > >How-To-Repeat: > > >Fix: > i commented out #include 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? Does compiling the following program: -------- #include #include int main () { } -------- give the same error? 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. State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Thu May 7 10:16:28 PDT 1998 State-Changed-Why: Broken compiler. From: Marc Slemko To: Apache bugs database Cc: Subject: Re: os-bsdi/2196: do not #include (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 To: Marc Slemko Subject: Re: os-bsdi/2196: do not #include 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 > > . > > this causes a declaration conflict for sys_siglist, which is also provided in > > unistd.h. > > >Fix: > > i commented out #include 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 > #include > > 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 jsd@gamespot.com ----------------------------------------------------------------------- Plan: Eat right, exercise regularly, die anyway. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]