DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-id:content-transfer-encoding
	:mime-version; q=dns; s=default; b=Yn3Lai5ZFKIqlPpjbZwCgkbN0pmMr
	MUnix0D560lwvQU6NAboD8ALyDCoTJueaillYdo8FzPadXPP0fpKu3lmJYkWoN9r
	0jety99BCE3BLOgaPFlqHrNJP9bPc5fygipVwLIo/7AhsHQauzUewrI8TvBeMcml
	CZyb9Ml1jU6QDs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: latest lighttpd (1.4.45) not working on Windows 10 Home Edition
Date: Fri, 7 Dec 2018 15:06:45 +0000
Message-ID: <0294dd4d-bc9c-5d95-6928-d1a8eeb36035@cornell.edu>
References: <CP2P152MB1793FE349C004422EE55A47FDCD20@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM> <CP2P152MB17938D9384DEE514E2F0BE3EDCAA0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM>
In-Reply-To: <CP2P152MB17938D9384DEE514E2F0BE3EDCAA0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM>
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
received-spf: None (protection.outlook.com: cornell.edu does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <EB3D1339397C7E4C8E72CD5B60E820B4@namprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

[Please don't top-post on this list.]

On 12/7/2018 9:13 AM, Alejandro Benitez wrote:
> Hi,
> 
> I'd like to add more information to the report.
> 
> With the help of the IRC support channel I've managed to successfully
> run a build of a later version of lighttpd (v 1.4.52) which is the
> latest tarball available at
> 
> https://www.lighttpd.net/download/
> 
> with the following build configuration
> 
> `./configure --without-bzip2 --with-openssl --with-lua`
> 
> The build is quite identical to the Cygwin build; I did not have to
> tweak my configuration files and everything worked as expected, whereas
> the current Cygwin package (v 1.4.45) shows the behavior I previously
> reported.

Out of curiosity, I downloaded the source for the Cygwin build, and your build 
is not identical with it.  If your goal is to provide useful information for the 
lighttpd maintainer, you should use the same configure options that he used.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple