Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 29 Jul 2003 13:03:04 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.1: unzip problems with binary files in archive Message-ID: <20030729170304.GA4137@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <16165 DOT 33853 DOT 968862 DOT 592625 AT phish DOT entomo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16165.33853.968862.592625@phish.entomo.com> User-Agent: Mutt/1.4.1i On Mon, Jul 28, 2003 at 01:14:53PM -0700, David Rothenberger wrote: >This problem occurs with the 1.5.1 DLL and the latest test packages >for zip and unzip. Everything works fine with 1.3.22. It also >works okay with 1.5.1 and the Curr versions of zip/unzip. Btw, I was able to reproduce this after refreshing my system with the test version of unzip. I was certain that I'd previously updated everything to test versions but apparently I hadn't. Sorry for creating confusion. The problem, as David has discovered, is that the prototype for lseek was not being used in unzip. This is a real lack in unzip's auto configuration, or lack thereof. cgf -- 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/