public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: apr: enable threads?
Date: Thu, 21 May 2015 22:12:00 -0000	[thread overview]
Message-ID: <1432241358.3296.4.camel@cygwin.com> (raw)
In-Reply-To: <555E3F58.7020302@acm.org>

On Thu, 2015-05-21 at 13:26 -0700, David Rothenberger wrote:
> Yaakov Selkowitz wrote:
> > I am looking at upgrading Apache httpd to 2.4, and it is clear that this
> > has not even attempted to be built with an APR without threads support.
> > While I may be able to get it to compile as-is, I have serious concerns
> > that it will not operate as designed, particularly wrt mod_proxy.
> > 
> > What exactly is blocking the enablement of threads support in APR?
> 
> The last time I tried it, the tests for subversion failed when threads
> were turned on in APR.

Would you mind trying again, and let's see if we can work out any
issues?  The fact that httpd won't build cleanly with APR threads
disabled makes me worry that nobody is really supporting this
configuration anymore.

Also, this would seem to indicate that we're missing something in
apr-util:

configure: WARNING: Your APR does not include SSL/EVP support. To enable
it: configure --with-crypto

--
Yaakov





--
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:[~2015-05-21 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 20:03 Yaakov Selkowitz
2015-05-21 20:49 ` David Rothenberger
2015-05-21 22:12   ` Yaakov Selkowitz [this message]
2015-05-21 23:12     ` David Rothenberger
2015-05-26  8:27       ` David Rothenberger
2015-05-29 21:49         ` Yaakov Selkowitz

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=1432241358.3296.4.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --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).