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

RE: [Bug] NO_INTPTR_T not being honoured in compat/regex/regcomp.c

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Jan 1, 2018, 22:12 UTC
Message-ID
<004a01d3834d$91bf2520$b53d6f60$@nexbridge.com>
In-Reply-To
<CAPig+cQ_H20ON0usig-FWj7YVF_AOR_yvBRhXJeFmRv_w7pZAw@mail.gmail.com>
On January 1, 2018 4:51 PM Eric Sunshine wrote:
Show 11 quoted lines
> On Mon, Jan 1, 2018 at 4:21 PM, Randall S. Becker
> <rsbecker@nexbridge.com> wrote:
> > * I have defined NO_INTPTR_T = UnfortunatelyYes in config.mak.uname
> > for my platform. The c99 compiler I have does not define it.
> > * The code compiles except for compat/regex/regcomp.c - not sure why
> > this is being used since I have also *not* defined NO_REGEX because
> > regex is sane here.
> 
> Presumably you're compiling for NonStop? config.mak.uname defines
> NO_REGEX for that platform (it also defines NO_INTPTR_T). git-blame points
> at 6c109904bc (Port to HP NonStop, 2012-09-19).
I got rid of that entry 3 years ago but did not contribute the updates because there are many other platform dependencies including FLOSS. Caution: that particular commit is not usable or useful on current NonStop operating systems.
Previous: Eric SunshineNext: Randall S. Becker
Message 3 of 4 in “[Bug] NO_INTPTR_T not being honoured in compat/regex/regcomp.c”
  1. Randall S. BeckerJan 1, 2018
  2. Eric SunshineJan 1, 2018
  3. Randall S. BeckerJan 1, 2018
  4. Randall S. BeckerJan 2, 2018

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.