Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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:	<42B191D3.E76B6DF3@dessent.net>
Date:	Thu, 16 Jun 2005 07:50:59 -0700
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Any chance to get Apache 2.0.xx working on cygwin?
References:	<508101312 AT web DOT de>
X-Spam-Report:	-5.8/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.1 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Andreas Eibach wrote:

>  This is VERY bad. You can only search for "Apache and 2 and 0 and 54", but not for apache and 2.0.54 (read 2 dot 0 dot 54 _in this order_). Quotes aren't accepted either; I think as the mailing lists archives are that important and used so much, there should at least be an exact match. No user wants to delve through 500 or 1000 messages with 450 or 950 of them irrelevant. (Rant over.)

The htdig on cygwin.com is pretty bad.  I always use google to search
the archives.  You can do this easily with a query of:

site:cygwin.com inurl:cygwin inurl:ml <query words here>

You can even use more "inurl:"s to restrict by year/month since those
are part of the URL.  In addition, the list is archived at many other
places, all of which have searches.  Three that come to mind are
gmane.org, marc.theaimsgroup.com, and mail-archive.com.

> Nice thing about Apache 2.0.54 is that it compiles OOTB without any errors. Nice.

See the other recent thread.  It will probably take some patching to
work.  Off the top of my head I'd suggest having cygserver installed and
running for both the configure/make and when starting apache, so that
you get the IPC functions.  For testing, it will probably be easier to
skip trying to run it as a service and get it running first when just
starting it from the prompt.  Make sure it's not trying to switch user
accounts though because this will not work outside of the SYSTEM
account.  Alternatively you can try starting it from a SYSTEM-shell
(search archives) which will simulate the service-startup environment
and allow for easier debugging of why it won't start.

Brian

--
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/

- Raw text -