git/list[1] front-page[2] threads[3] people[4] search[5] about
 

NO_REGEX defaults on obscure platforms

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Sep 8, 2010, 15:12 UTC
Message-ID
<AANLkTimYY_KHwqWWXTxFqW67FHYtJJkLuA-6WVc6wzO5@mail.gmail.com>
On Mon, Sep 6, 2010 at 07:41, Junio C Hamano <gitster@pobox.com> wrote:
> There are a few leftover bits in 'next' that need to be merged to 'master'
> before we declare a real -rc cycle, so tonight's pushout is -rc0.

One thing that's almost certainly wrong in v1.7.3-rc0 is the NO_REGEX defaults. It's a non-issue for people who run the configure script, but the Makefile probably has the wrong defaults on some obscure platforms.

I've CC'd people involved in Tru64, UnixWare, SCO, HP/UX, IRIX etc. It would be really useful if you could:

  1. Get v1.7.3-rc0
  2. Compile with the defaults, and NO_REGEX=YesPlease
  3. Run `cd t && ./t7008-grep-binary.sh` and report the results.
That test is probably failing on some of these platforms.

Alternatively, just check for REG_STARTEND in regex.h (or the includes it pulls in):

    $ grep REG_STARTEND /usr/include/regex.h
    #define REG_STARTEND (1 << 2)
Next: Brandon Casey
Message 1 of 6 in “NO_REGEX defaults on obscure platforms”
  1. Ævar Arnfjörð BjarmasonSep 8, 2010
  2. Brandon CaseySep 8, 2010
  3. Jakub NarebskiSep 8, 2010
  4. 1/2 t/t7008: workaround broken handling of \000 by printf on IRIXBrandon Casey, Sep 9, 2010
  5. 2/2 Makefile: use compat regex on IRIX 6.5Brandon Casey, Sep 9, 2010
  6. Junio C HamanoSep 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.