Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <001a01c2b248$8d5766a0$ba36fea9@oemcomputer>
From: "Sascha Sommer" <saschasommer AT freenet DOT de>
To: <cygwin AT cygwin DOT com>
References: <011401c2b1e4$67153c60$e185fea9 AT oemcomputer> <20030101235623 DOT GA24893 AT redhat DOT com>
Subject: Re: read() syscall broken on faster cpu?
Date: Thu, 2 Jan 2003 11:20:18 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

> On Wed, Jan 01, 2003 at 11:23:24PM +0100, Sascha Sommer wrote:
> >Is it possible, that the read() syscall sometimes doesn't work correctly
on
> >newer cpus?
>
> No.
>
> cgf
>
sorry my fault, cygwin was configured wrong on these machines....

S. Sommer


--
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/