Received: (qmail 9238 invoked by uid 2012); 25 Aug 1999 18:48:33 -0000
Message-Id: <19990825184833.9237.qmail@hyperreal.org>
Date: 25 Aug 1999 18:48:33 -0000
From: Mark Miller <markm@swoon.net>
Reply-To: markm@swoon.net
To: apbugs@hyperreal.org
Subject: Missing definition of rlim_t in ap_config.h
X-Send-Pr-Version: 3.2

>Number:         4906
>Category:       os-next
>Synopsis:       Missing definition of rlim_t in ap_config.h
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Aug 25 11:50:01 PDT 1999
>Last-Modified:  Sun Nov 28 05:30:01 PST 1999
>Originator:     markm@swoon.net
>Organization:
apache
>Release:        1.3.9
>Environment:
OPENSTEP/Mach 4.2
>Description:
The addition of rlim_t in http_core.c presented an undefined type when building apache 1.3.9 on OPENSTEP/Mach 4.2.
>How-To-Repeat:
Build a standard apache 1.3.9 on OPENSTEP/Mach 4.2.
>Fix:
Adding a "typedef int rlim_t;" to the "#elif defined(NEXT)" section (line 351) in ap_cofig.h fixes the problem.
>Audit-Trail:

From: "Ralf S. Engelschall" <rse@engelschall.com>
To: apbugs@apache.org
Cc:  Subject: Re: os-next/4906: Missing definition of rlim_t in ap_config.h
Date: Sun, 28 Nov 1999 14:28:18 +0100

 In article <19990825184833.9237.qmail@hyperreal.org> you wrote:
  
 >>Number:         4906
 >>Category:       os-next
 >>Synopsis:       Missing definition of rlim_t in ap_config.h
 > [...]
 > Adding a "typedef int rlim_t;" to the "#elif defined(NEXT)" section (line
 > 351) in ap_cofig.h fixes the problem.
 
 Now fixed for Apache 1.3.10.
 Thanks for your feedback.
                                        Ralf S. Engelschall
                                        rse@engelschall.com
                                        www.engelschall.com
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]