git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Gerhard Grimm <gerhard.grimm@detec.com>, Git List <git@vger.kernel.org>
Subject: Re: Problems with git 1.8.5.3 on HP-UX 11.11
Date: Fri, 28 Mar 2014 16:02:19 -0400	[thread overview]
Message-ID: <20140328200218.GA3145@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPig+cQKZ-oKTQ4Y2=qDaeQRXVZYOKRcSadOx2RwfjCziuu6fw@mail.gmail.com>

On Fri, Mar 28, 2014 at 03:43:29PM -0400, Eric Sunshine wrote:

> On Fri, Mar 28, 2014 at 3:01 PM, Jeff King <peff@peff.net> wrote:
> > On Fri, Mar 28, 2014 at 11:09:14AM -0000, Gerhard Grimm wrote:
> >> git submodule init
> >>
> >> fails with the output
> >>
> >>     Assertion failed: err == REG_ESPACE, file compat/regex/regexec.c, line 1096
> >>     No submodule mapping found in .gitmodules for path 'module'
> >
> > The regexes we use here are not particularly complicated. So either
> > there is a bug (but nobody else has reported anything on any other
> > platform) or your system regex library has some problem with what we are
> > feeding it. The simplest solution may be to compile with:
> >
> >   NO_REGEX=YesPlease
> >
> > which will build and use the glibc implementation in compat/regex
> > instead.
> 
> Based upon the assertion-failure message, it looks like he's already
> using compat/regex.

Heh, I didn't even notice that. I just looked at all of the libc calls
at the top of the backtrace, but of course that is just from assert() on
up.

So now it seems doubly odd to me, since it is running the same regex
library that is used elsewhere.

-Peff

      reply	other threads:[~2014-03-28 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9D24AD27564FAE4CB8D0C15D080DEFCB0106A89226@m4ukex08.intranet.macro4.com>
2014-03-28 11:09 ` Problems with git 1.8.5.3 on HP-UX 11.11 Gerhard Grimm
2014-03-28 11:48   ` Thomas Ackermann
2014-03-28 19:01   ` Jeff King
2014-03-28 19:43     ` Eric Sunshine
2014-03-28 20:02       ` Jeff King [this message]

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=20140328200218.GA3145@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=gerhard.grimm@detec.com \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.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 NNTP newsgroup(s).