This is the mail archive of the
mailing list for the Cygwin project.
Re: GCC v2.95 doesn't work (a bug?)
- To: Paul Sokolovsky <paul-ml at is dot lg dot ua>
- Subject: Re: GCC v2.95 doesn't work (a bug?)
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Sun, 10 Oct 1999 18:05:51 -0400
- Cc: bughz at iname dot com, Teofilis Martisius <smart at org dot ktu dot lt>, cygwin at sourceware dot cygnus dot com
- References: <991009105213CW.email@example.com> <firstname.lastname@example.org>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Sun, Oct 10, 1999 at 06:37:06PM +0300, Paul Sokolovsky wrote:
>If you use Win95/98 it's same old bug with lseek()-past-end-of-file.
>POSIX requires that if such call was made followed by write(), skipped
>space to be zeroed. But win9x leaves previous physical media contents
>there. That almost surely hits when producing dlls, and I submitted
>work-around-like patch for that (see >http://www.is.lg.ua/~paul/devel/binutils.html),
>but it specially applies only to PE files, not generic COFF. After
>that I several times saw problem described by you, but only during
>experiments and never in real work ;-) , so I didn't bother to fix it
DJ fixed the "lseek past end" last summer for his first official act as
a cygwin developer.
AFAIK, this problem should not be an issue if gcc is using cygwin.
Want to unsubscribe from this list?
Send a message to email@example.com