Received: (qmail 9121 invoked by uid 2012); 28 Jul 1998 10:26:48 -0000
Message-Id: <19980728102648.9120.qmail@hyperreal.org>
Date: 28 Jul 1998 10:26:48 -0000
From: Samuel Liddicott <sam@cmapbellsci.co.uk>
Reply-To: sam@cmapbellsci.co.uk
To: apbugs@hyperreal.org
Subject: SCO dev kit error (NOT apache error)
X-Send-Pr-Version: 3.2

>Number:         2725
>Category:       os-sco
>Synopsis:       SCO dev kit error (NOT apache error)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Jul 28 03:30:01 PDT 1998
>Last-Modified:  Wed Mar 24 09:56:02 PST 1999
>Originator:     sam@cmapbellsci.co.uk
>Organization:
>Release:        1.3.1
>Environment:
SCO 3.2v4.2 with SCO compiler
>Description:
The timeval struct is defined in two SCO .h files (same definition).
sys/time.h and sys/select.h

One of the apache files includes both these .h files, and so compilation fails with an error that timeval is being redifined.
>How-To-Repeat:
Compile on same platform
>Fix:
edit /usr/include/sys/time.h and /usr/include/sys/select.h to have the timeval declaration change FROM

struct timeval {
        long            tv_sec; /* seconds */
        long            tv_usec;/* and microseconds */
};        

TO

#ifndef DIDTIMEVAL
#define DIDTIMEVAL
struct timeval {
        long            tv_sec; /* seconds */
        long            tv_usec;/* and microseconds */
};
#endif          

(in BOTH .h files)

Then it will compile OK.
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: coar
State-Changed-When: Wed Mar 24 09:56:02 PST 1999
State-Changed-Why:

Since this is a SCO problem, there's not much we can
do about it.  Please report it to SCO if you haven't
already.  Thanks for using Apache!

>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 leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]