X-Spam-Check-By: sourceware.org Message-ID: <4461538B.3010308@cwilson.fastmail.fm> Date: Tue, 09 May 2006 22:44:27 -0400 From: Charles Wilson User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Test: zip-2.31 and unzip-5.52 References: <4460C4B4 DOT 1070002 AT bellsouth DOT net> In-Reply-To: <4460C4B4.1070002@bellsouth.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Charles D. Russell wrote: > I use zip and gzip for backup files, where a bug is unlikely to be > detected before the problem is catastrophic. Thus I like to stick to > old, well-tested versions, and am interested in understanding where > problems might arise. I would have thought that the cygwin executable > would be the same as that obtained by taking the standard source and > running make. > Do you really think that every cygwin package compiles out-of-box with no changes? Not even close to true! In this case, there are a number of changes -- even in the "old, well-tested versions" that you've been happily using. For your perusal, I've attached the patches -- of course, you could easily have downloaded the -src packages and extracted these yourself. The changes boil down to three areas: (1) ensuring we do not use windows-isms when we should be using cygwin/posix-isms (2) ensuring that files are opened in binary, not text, mode (e.g. ensuring we don't use posix-isms when we should use windows-isms!), and (3) routine changes to the build system (enabling DESTDIR installs, building outside the source directory, .exe extensions on applications, etc) > What is special about cygwin that requires patches? Notwithstanding the 'use posix instead of windows' ethos, we ARE, undeniably, running on windows. That's special. Most non-autotool-based packages (like zip and unzip) which have been ported to windows, do so making assumptions about make/nmake, msvc-cl/gcc, etc. These assumptions are usually wrong for cygwin, as we are a hybrid blend with posix and gcc features, but also some windows restrictions. Why does cygwin require patches, indeed... -- Chuck -- 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/