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:	<00ab01c32b5c$aeb41950$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<004201c32902$3e92b020$78d96f83 AT pomello> <20030602133202 DOT GC30498 AT redhat DOT com> <bbl3cu$ph4$1 AT main DOT gmane DOT org> <20030605115804 DOT GL875 AT cygbert DOT vinschen DOT de>
Subject:	Re: Sparse file criteria malfunction - binutils produces sparse .exe & .dll files
Date:	Thu, 5 Jun 2003 13:19:16 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165
X-Cam-ScannerAdmin:	mail-scanner-support AT ucs DOT cam DOT ac DOT uk
X-Cam-AntiVirus:	Not scanned
X-Cam-SpamDetails:

Corinna Vinschen wrote:
> On Wed, Jun 04, 2003 at 05:33:46PM +0200, Markus Mauhart wrote:
>> Now it has been proven that each cygwin installation manipulating 1000s
of
>> files only suffers from this "feature"; not to mention that it breaks
>> winfile.exe :-(((.
>
> The next Cygwin version will produce sparse files only if the application
> decides to write 64K or more beyond EOF.

Unfortunately, ld does seems to so this when writing PE files (well, I'm
guessing libbfd, since strip does as well).
No, I haven't verified this in the source - I've got university exams, so
I'm a little busy!

Max.


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