Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3BD1AF95.2080701@digicool.com> Date: Sat, 20 Oct 2001 13:08:37 -0400 From: Chris McDonough Reply-To: chrism AT zope DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010801 X-Accept-Language: en-us MIME-Version: 1.0 To: Robert Collins CC: nhv AT cape DOT com, "'Chris McDonough'" , zope-dev AT zope DOT org, cygwin AT cygwin DOT com Subject: Re: [Zope-dev] Zope & Cygwin References: <008201c15833$8debc5e0$a300a8c0 AT nhv> <007c01c15948$7ee3a4d0$0200a8c0 AT lifelesswks> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Possibly dumb question - Are there binary distributions of v 1.1.8 of cygwin1.dll available from cygwin.org anywhere or should I compile it from source? I looked around for a while on there and it seems that I'd need to use CVS to check out a 1.1.8-tagged branch and compile to get back to that revision. > This may well be related to the reported breakage with cygwin more > recent than 1.3.1/1.1.8 and apache. I've got a faulting setup with squid > showing the same thing, but no time to debug (yet). You might consider > testing with 1.1.8 and seeing if that fixes the issue. If reverting does > 'fix' this, and the time to cause the fault is relatively short, > consider doing a binary CVS search to find the commit that broke it. > > Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/