git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: "git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: HTTP tests fail on OS X
Date: Fri, 21 Jun 2013 00:49:54 -0400	[thread overview]
Message-ID: <20130621044953.GA5962@sigill.intra.peff.net> (raw)
In-Reply-To: <26902D6D-D105-4943-BC67-461CEF82D888@gernhardtsoftware.com>

On Fri, Jun 21, 2013 at 12:45:25AM -0400, Brian Gernhardt wrote:

> > I'm not sure if there is something different between 2.2.16 and 2.2.22,
> > or something with the particular build. Here's my -V output, in case it
> > helps:
> [...]
> Doesn't look terribly different from mine.

It turns out that 2.2.22 is in Debian testing, so it was easy for me to
downgrade from 2.4 and try it. Seems to also work fine for me. So I
don't think it's an apache version issue.

I also installed the prefork mpm in case that was part of the problem.
But it all seems fine here, and my build parameters look quite similar
to yours.

I'm not sure what else to look at...I guess try ratcheting up the
debugging/log level on your failing copy and see if it prints anything
useful.

-Peff

  reply	other threads:[~2013-06-21  4:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  4:27 HTTP tests fail on OS X Brian Gernhardt
2013-06-21  4:30 ` Jeff King
2013-06-21  4:42   ` Jeff King
2013-06-21  4:45     ` Brian Gernhardt
2013-06-21  4:49       ` Jeff King [this message]
2013-06-21 17:03         ` Brian Gernhardt
2013-06-21 18:03           ` Jeff King
2013-06-21 18:08             ` Brian Gernhardt
2013-06-21 18:12               ` [PATCH] lib-httpd/apache.conf: check version only after mod_version loads Jeff King
2013-06-21 18:15                 ` Brian Gernhardt
2013-06-21 18:18                   ` Jeff King
2013-06-21 20:59                 ` Junio C Hamano

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=20130621044953.GA5962@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=brian@gernhardtsoftware.com \
    --cc=git@vger.kernel.org \
    /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 NNTP newsgroup(s).