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:	<3F20A3DE.B325E08F@acm.org>
Date:	Thu, 24 Jul 2003 20:28:30 -0700
From:	David Rothenberger <daveroth AT acm DOT org>
Reply-To:	cygwin AT cygwin DOT com
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.0: Problem with fseeko() after fdopen() (gold star alert)
References:	<16160 DOT 1351 DOT 752705 DOT 773318 AT phish DOT entomo DOT com> <20030725024622 DOT GA9919 AT redhat DOT com>

Christopher Faylor wrote:
> [snip]
> I've submitted a patch request to fix this to the newlib mailing list
> which I expect to fix the problem.  It does cause patch to operate
> correctly when linked with a new cygwin dll.

I'm glad you posted.  I was just about to try writing fdopen64 myself. 
I just figured out how the aliasing to the 64-bit I/O stuff worked. 
I've been in Java land too long; I've forgotten all this linking stuff.

Back to banging my head on the rxvt/XEmacs copy/paste problem.

Dave

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -