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 From: "Dave Korn" To: Subject: RE: httpd-2.0.52 (Apache2) testers wanted / maintainer searched Date: Wed, 1 Dec 2004 14:43:56 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <41ADCE37.5070509@familiehaase.de> Message-ID: X-OriginalArrivalTime: 01 Dec 2004 14:43:56.0296 (UTC) FILETIME=[2F6CC880:01C4D7B4] > -----Original Message----- > From: cygwin-owner On Behalf Of Gerrit P. Haase > Sent: 01 December 2004 13:59 > > /oem-install/httpd-2.0.52 $ patch -p1 -i ../httpd-2.0.52-1.patch > > patching file CYGWIN-PATCHES/README > > ....ellided > > patching file srclib/apr/configure.in > > > > Looks good. > > > > --------------- > > But now how do I run this build-script and from where? > > Or should I be running ./configure at this point. > > In the source package are three files, the original source, the > paptchfile and the script, after extracting the source run: > $ ./httpd-2.0.52-1.sh prep > This extracts the source and aplies the patch > $ ./httpd-2.0.52-1.sh conf > $ ./httpd-2.0.52-1.sh build > $ ./httpd-2.0.52-1.sh install > ... > > See the bottom of the script, there is an option 'all' which runs > all needed script targets, there are some more eg. 'strip'. > It should work to run > $ ./httpd-2.0.52-1.sh all > which will create a new binary tarball and a new source tarball. If this script has patched configure.in, won't the whole thing need regenerating with the auto-* toolset? Or does the script take care of that too? cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/