Received: (qmail 19477 invoked by uid 2012); 18 May 1998 14:04:48 -0000
Message-Id: <19980518140448.19476.qmail@hyperreal.org>
Date: 18 May 1998 14:04:48 -0000
From: Justin Pope <jnpope@dali.ppco.com>
Reply-To: jnpope@dali.ppco.com
To: apbugs@hyperreal.org
Subject: GCC compile error, readv/writev
X-Send-Pr-Version: 3.2

>Number:         2244
>Category:       os-irix
>Synopsis:       GCC compile error, readv/writev
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon May 18 07:10:00 PDT 1998
>Last-Modified:  Mon May 25 10:30:01 PDT 1998
>Originator:     jnpope@dali.ppco.com
>Organization:
>Release:        1.2.6
>Environment:
IRIX 6.2, gcc 2.7.2.2
>Description:
Output from make command:

 ...
 In file included from buff.c:66:
 /usr/include/sys/uio.h:34: conflicting types for `readv'
 /usr/ppco/GNU/lib/gcc-lib/mips-sgi-irix5.3/2.7.2.2.f.2/include/unistd.h:157: previous declaration of `readv'

Looks like another cc vs. gcc difference.
>How-To-Repeat:

>Fix:
Adding #define NO_WRITEV in the IRIX section of conf.h fixes the problem for us.
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: dgaudet
State-Changed-When: Mon May 25 10:26:30 PDT 1998
State-Changed-Why:
User is using gcc compiled against irix 5.3 on an irix 6.2
machine.  That is a broken configuration.

Dean

From: Dean Gaudet <dgaudet@arctic.org>
To: Justin Pope <jnpope@dali.ppco.com>
Cc: apbugs@hyperreal.org
Subject: Re: os-irix/2244: GCC compile error, readv/writev
Date: Mon, 25 May 1998 11:07:59 -0700 (PDT)

 This should be put in the FAQ so many people run into it. 
 
 On 18 May 1998, Justin Pope wrote:
 
 > >Environment:
 > IRIX 6.2, gcc 2.7.2.2
 >  ...
 >  In file included from buff.c:66:
 >  /usr/include/sys/uio.h:34: conflicting types for `readv'
 >  /usr/ppco/GNU/lib/gcc-lib/mips-sgi-irix5.3/2.7.2.2.f.2/include/unistd.h:157: previous declaration of `readv'
 
 IRIX version 6.2, gcc built against 5.3.  This is wrong.  gcc is
 intimately tied with the version of the operating system it is built for. 
 Rebuild gcc on 6.2 and the problem will go away. 
 
 You don't want to run with NO_WRITEV -- it can cause painful network
 traffic against HTTP/1.1 clients (IE4 for example).
 
 Dean
 
>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. ]