You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Richard Stagg <st...@lentil.org> on 1998/11/03 16:43:33 UTC
config/3336: Porting Apache to Cyberguard V2 machines
>Number: 3336
>Category: config
>Synopsis: Porting Apache to Cyberguard V2 machines
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: change-request
>Submitter-Id: apache
>Arrival-Date: Tue Nov 3 07:50:01 PST 1998
>Last-Modified:
>Originator: stagg@lentil.org
>Organization:
apache
>Release: 1.3
>Environment:
CX/SX 6.2 Cyberguard Revision 2 machines patch 8 and above
Running Harris CC (very weird C compiler)
>Description:
It's not possible to compile Apache on a Cyberguard from a standard
package, as the "grok" doesn't know about the operating system and the
options for compilation are a bit weird.
>How-To-Repeat:
Just try it!
>Fix:
Yeh - I've worked out the porting. If you were to implement the following
changes, it'd work "out of the box".
Add this paragraph to "src/Configure"
m88k-*-CX/SX|*|CYBER)
OS='Cyberguard CX/SX'
CFLAGS="$CFLAGS -D_CX_SX -Xa"
DEF_WANTTHISREGEX=yes
CC='cc'
RANLIB="true"
;;
In src/include/conf.h, add (somewhere in the list of OS specific definitions)
#elif defined(_CX_SX)
#define JMP_BUF sigjmp_buf
#include <sys/types.h>
#include <sys/time.h>
This will now permit a normal Configure/Make build of Apache.
NB: This is NOT tested on Cyberguard Version 4 machines (but they run
SCO unix anyway).
I hope this is considered worthy of inclusion.
Regards
Richard Stagg
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> 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! ]