public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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, 07 Dec 2018 15:06:00 -0000	[thread overview]
Message-ID: <0294dd4d-bc9c-5d95-6928-d1a8eeb36035@cornell.edu> (raw)
In-Reply-To: <CP2P152MB17938D9384DEE514E2F0BE3EDCAA0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM>

[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

  reply	other threads:[~2018-12-07 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 14:31 Alejandro Benitez
2018-12-07 14:14 ` Alejandro Benitez
2018-12-07 15:06   ` Ken Brown [this message]
2018-12-08  0:29     ` Alejandro Benitez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0294dd4d-bc9c-5d95-6928-d1a8eeb36035@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).