Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <00ab01c32b5c$aeb41950$78d96f83@pomello> From: "Max Bowsher" To: References: <004201c32902$3e92b020$78d96f83@pomello> <20030602133202.GC30498@redhat.com> <20030605115804.GL875@cygbert.vinschen.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 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.1165 X-Cam-ScannerAdmin: mail-scanner-support@ucs.cam.ac.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/