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 Date: Mon, 2 Jun 2003 09:32:02 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Sparse file criteria malfunction - binutils produces sparse .exe & .dll files Message-ID: <20030602133202.GC30498@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <004201c32902$3e92b020$78d96f83@pomello> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004201c32902$3e92b020$78d96f83@pomello> User-Agent: Mutt/1.4.1i On Mon, Jun 02, 2003 at 01:26:50PM +0100, Max Bowsher wrote: >$ uname -svr >CYGWIN_NT-5.1 1.5.0(0.86/3/2) 2003-06-02 00:41 > >The new sparse file heuristic is being triggered by the way binutils writes >.exe and .dll files. > >I'm unsure this could be worked around. Any ideas? Since you are the principal complainer about this particular feature, why don't you analyze *what* is causing this in binutils? Is ld *really* writing files beyond EOF? Or is something else going on? -- 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/