Received: (qmail 7291 invoked by uid 2012); 19 Oct 1998 19:05:30 -0000 Message-Id: <19981019190530.7290.qmail@hyperreal.org> Date: 19 Oct 1998 19:05:30 -0000 From: Amiel Lee Yee Reply-To: Amiel.LeeYee@cigna.com To: apbugs@hyperreal.org Subject: ap_config.h (DGUX section needs to be modified). X-Send-Pr-Version: 3.2 >Number: 3247 >Category: os-dgux >Synopsis: ap_config.h (DGUX section needs to be modified). >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Oct 19 12:10:02 PDT 1998 >Last-Modified: Fri Dec 11 19:07:18 PST 1998 >Originator: Amiel.LeeYee@cigna.com >Organization: >Release: 1.3.3 >Environment: OS : dgux R4.20MU02 generic AViiON PentiumPro (Data General Unix) CC : gcc version 2.7.2 (ix86 DG/ux, DG-2.7.2.9, Feb 3 1998) >Description: There are two versions of DGUX. There is the Intel version and the Motorola version. The Intel version has support for strncasecmp, and strcasecmp in the string.h header file. I am not to sure of the Motorola version. The fix that I am suggesting will work on an Intel box. >How-To-Repeat: >Fix: I have changed the DGUX section to the following following: #elif defined(DGUX) #define NO_KILLPG #undef NO_SETSID #undef NEED_STRDUP #ifdef _IX86_DG /* Added to see if it is Intel */ #undef NEED_STRCASECMP #undef NEED_STRNCASECMP #else #define NEED_STRCASECMP #define NEED_STRNCASECMP #endif /* End of fix */ #define bzero(a,b) memset(a,0,b) /* A lot of SVR4 systems need this */ #define USE_FCNTL_SERIALIZED_ACCEPT #define ap_inet_addr inet_network #define HAVE_SYSLOG 1 >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: coar State-Changed-When: Wed Oct 21 09:00:00 PDT 1998 State-Changed-Why: Thanks for the information. Could you please re-generate the changes as a unified diff (diff -u) and reply to this message with it? Be sure to Cc , and don't change the Subject: line at all. Category-Changed-From-To: general-os-dgux Category-Changed-By: coar Category-Changed-When: Wed Oct 21 09:00:00 PDT 1998 From: "Lee Yee, Amiel" To: "'coar@apache.org'" Cc: "'apbugs@Apache.Org'" Subject: RE: os-dgux/3247: ap_config.h (DGUX section needs to be modified) . Date: Fri, 23 Oct 1998 11:44:14 -0400 Here is the diff that you requested. --- ap_config_old.h Fri Oct 23 09:37:55 1998 +++ ap_config.h Fri Oct 23 09:39:05 1998 @@ -570,8 +570,13 @@ #define NO_KILLPG #undef NO_SETSID #undef NEED_STRDUP +#ifdef _IX86_DG +#undef NEED_STRCASECMP +#undef NEED_STRNCASECMP +#else #define NEED_STRCASECMP #define NEED_STRNCASECMP +#endif #define bzero(a,b) memset(a,0,b) /* A lot of SVR4 systems need this */ #define USE_FCNTL_SERIALIZED_ACCEPT > -----Original Message----- > From: coar@apache.org [SMTP:coar@apache.org] > Sent: Wednesday, October 21, 1998 12:01 PM > To: amiel.leeyee@cigna.com; apache-bugdb@apache.org; coar@apache.org > Subject: Re: os-dgux/3247: ap_config.h (DGUX section needs to be > modified). > > [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. ] > [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! ] > > > Synopsis: ap_config.h (DGUX section needs to be modified). > > State-Changed-From-To: open-feedback > State-Changed-By: coar > State-Changed-When: Wed Oct 21 09:00:00 PDT 1998 > State-Changed-Why: > > Thanks for the information. Could you please re-generate > the changes as a unified diff (diff -u) and reply to this > message with it? Be sure to Cc , and > don't change the Subject: line at all. > > Category-Changed-From-To: general-os-dgux > Category-Changed-By: coar > Category-Changed-When: Wed Oct 21 09:00:00 PDT 1998 > State-Changed-From-To: feedback-closed State-Changed-By: fielding State-Changed-When: Fri Dec 11 19:07:18 PST 1998 State-Changed-Why: Thanks for the patch -- it will be included in the next release. >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. ] [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! ]