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 Message-ID: <04d401c57540$b53e8fa0$e6ec6f83@chimaera> From: "Max Bowsher" To: "Gerrit P. Haase" Cc: References: <511859934 AT web DOT de> <42B5FBA1 DOT 3090300 AT familiehaase DOT de> <037d01c57530$c8aa4850$e6ec6f83 AT chimaera> <42B619D0 DOT 8030104 AT familiehaase DOT de> Subject: Re: Any chance to get Apache 2.0.xx working on cygwin? Date: Mon, 20 Jun 2005 03:35:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Gerrit P. Haase wrote: > Max Bowsher wrote: > >> Gerrit P. Haase wrote: >> >>> I found the source / build tree, it is still around anyway. The >>> compressed tarball with the patch is about 400k. May I send >>> you the patchfile and script (as PM)? >> >> >> Eep! How did you get a patch that big? >> >> My actual "upstream modifications" patch is about 10k. (that's excluding >> the Cygwin-specific additional files) >> >> Is there lots of autogenerated churn in the patch? > > Yes, all the autoreconf changes and some helper scripts. I've deliberately kept the autoreconf changes out of mine, so I can see the important bits. > Does your package build shared modules and a shared core DLL? Yes. That was a critical thing for me, since I wanted to build additional modules (subversion) easily. I've ITP-ed now, if you want to have a look at it. 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/