Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <20020729142621.20666.qmail@web21006.mail.yahoo.com>
Date: Mon, 29 Jul 2002 07:26:21 -0700 (PDT)
From: Nicholas Wourms <nwourms AT yahoo DOT com>
Subject: Re: {IOV_MAX} symbols
To: "Ren�_M�ller_Fonseca" <fonseca AT mip DOT sdu DOT dk>, cygwin AT cygwin DOT com
In-Reply-To: <3D4513E0.20603@mip.sdu.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Ren�_M�ller_Fonseca <fonseca AT mip DOT sdu DOT dk> wrote:
> Since cygwin implements the XSI functions readv and writev; the
> symbols 
> _SC_IOV_MAX and _XOPEN_IOV_MAX MUST also be defined (IOV_MAX is
> already 
> defined).
> 
> /** Belongs in unistd.h. */
> #define _SC_IOV_MAX ???
> 
> /** Specifies the most restrictive value (belongs in limits.h). */
> #define _XOPEN_IOV_MAX 16
> 
> Don't forget to add support for _SC_IOV_MAX in sysconf.
> 
Ren�,

Your best bet would be to patch the cygwin source code from cvs and
generate a diff from that.  You can find out more about the process
here:

http://cygwin.com/contrib.html

You'll want to generate the diff and submit it to
cygwin-patches AT cygwin DOT com.  You might also want to provide a testcase
c program to demonstrate why these changes are needed.  Also,
referring to specific standards might help as well.  Note, if you
make less then 10 lines of changes to the cygwin code, you probably
do not need to submit a copyright assignment.

Cheers,
Nicholas

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/