Re: [7087] 4.2.0-pre-1

Re: [7087] 4.2.0-pre-1

[Peter Stephenson]

Danek Duvall wrote:
> Is there going to be any effort to incorporate into 4.2 Clint's patch in
> workers/16845, to link the libraries that only a module (and not the
> main zsh binary) depends on only to the module and not the zsh binary?
> It looks to me like the mail thread there had a little discussion, no
> real problems were found, but then it was dropped.

It used widely available but not necessarily universal `make'
extensions.

I certainly don't have any time to take on yet more configure
commitments myself, it's up to Clint.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited. 
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

Re: [7087] 4.2.0-pre-1

[Clint Adams]

> It used widely available but not necessarily universal `make'
> extensions.

> I certainly don't have any time to take on yet more configure
> commitments myself, it's up to Clint.

I'll take a stab at forward-porting it.  I suppose I can try to test
whether make(1) supports 'include', '.include', or neither, and trying
to cope with the situation.

Re: 4.2.0-pre-1

[Danek Duvall]

On Sat, Feb 28, 2004 at 01:52:36AM -0500, Clint Adams wrote:

> > It used widely available but not necessarily universal `make'
> > extensions.
> 
> > I certainly don't have any time to take on yet more configure
> > commitments myself, it's up to Clint.
> 
> I'll take a stab at forward-porting it.  I suppose I can try to test
> whether make(1) supports 'include', '.include', or neither, and trying
> to cope with the situation.

Was there anything wrong with Bart's suggestion to just copy the
necessary rules directly into the generated Makefile?

Danek

Re: 4.2.0-pre-1

[Clint Adams]

> Was there anything wrong with Bart's suggestion to just copy the
> necessary rules directly into the generated Makefile?

I'm not sure how to get the Makefile dependencies correct in that case, 
but otherwise it could work.

Re: 4.2.0-pre-1

[Peter Stephenson]

Ibraheem Umaru-Mohammed wrote:
> I have been unable to build zsh-4.2.0-pre-1, (or zsh-4.1.1) on AIX 5.2. Any
> help will be greatly appreciated. I have included the config.log, and the
> last few lines before failure - should you require any more details let me
> know.
>...
>         /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o init.o ini
> t.c
> "sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the en
> d of line.
> "signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the
>  end of line.
> "init.c", line 493.5: 1506-275 (S) Unexpected text 'int' encountered.
> make: The error code from the last command is 1.

Thanks for reporting this, although please send messages to
zsh-workers@sunsite.dk, not to me personally.

The code you must be executing looks uncompilable in standard C... not
surprising it didn't work.  Please do let us know about any more
failures, we only have a limited user base for AIX.

pws

Index: Src/init.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/init.c,v
retrieving revision 1.39
diff -u -r1.39 init.c
--- Src/init.c	15 Dec 2003 22:45:29 -0000	1.39
+++ Src/init.c	1 Mar 2004 10:37:40 -0000
@@ -481,6 +481,9 @@
 init_shout(void)
 {
     static char shoutbuf[BUFSIZ];
+#if defined(JOB_CONTROL) && defined(TIOCSETD) && defined(NTTYDISC)
+    int ldisc;
+#endif
 
     if (SHTTY == -1)
     {
@@ -490,8 +493,7 @@
     }
 
 #if defined(JOB_CONTROL) && defined(TIOCSETD) && defined(NTTYDISC)
-    int ldisc = NTTYDISC;
-
+    ldisc = NTTYDISC;
     ioctl(SHTTY, TIOCSETD, (char *)&ldisc);
 #endif
 
-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited. 
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

Re: 4.2.0-pre-1

[Ibraheem Umaru-Mohammed]

On [01/03/04 10:52 +0000], Peter Stephenson wrote:
> Ibraheem Umaru-Mohammed wrote:
> > I have been unable to build zsh-4.2.0-pre-1, (or zsh-4.1.1) on AIX 5.2. Any
> > help will be greatly appreciated. I have included the config.log, and the
> > last few lines before failure - should you require any more details let me
> > know.
> >...
> >         /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o init.o ini
> > t.c
> > "sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the en
> > d of line.
> > "signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the
> >  end of line.
> > "init.c", line 493.5: 1506-275 (S) Unexpected text 'int' encountered.
> > make: The error code from the last command is 1.
> 
> Thanks for reporting this, although please send messages to
> zsh-workers@sunsite.dk, not to me personally.
[...]

My apologies - I guess one can still get shy behind the mask of an email.

> The code you must be executing looks uncompilable in standard C... not
> surprising it didn't work.  Please do let us know about any more
> failures, we only have a limited user base for AIX.
> 

This makes sense, because of all the platforms I have access to at work
(Linux, Solaris, HPUX, and AIX), AIX 5.x is the only platform that zsh has 
failed to successfully compile under.

> pws
> 
> Index: Src/init.c
> ===================================================================
> RCS file: /cvsroot/zsh/zsh/Src/init.c,v
> retrieving revision 1.39
> diff -u -r1.39 init.c
> --- Src/init.c	15 Dec 2003 22:45:29 -0000	1.39
> +++ Src/init.c	1 Mar 2004 10:37:40 -0000
> @@ -481,6 +481,9 @@
>  init_shout(void)
>  {
>      static char shoutbuf[BUFSIZ];
> +#if defined(JOB_CONTROL) && defined(TIOCSETD) && defined(NTTYDISC)
> +    int ldisc;
> +#endif
>  
>      if (SHTTY == -1)
>      {
> @@ -490,8 +493,7 @@
>      }
>  
>  #if defined(JOB_CONTROL) && defined(TIOCSETD) && defined(NTTYDISC)
> -    int ldisc = NTTYDISC;
> -
> +    ldisc = NTTYDISC;
>      ioctl(SHTTY, TIOCSETD, (char *)&ldisc);
>  #endif
>  
[...]

Seem to have gotten further, but still falls over:

[--- build zsh on AIX 5.2 ---]
** NONE **:44% make
        cd . && /bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
Updated `zsh.mdh'.
Updated `termcap.mdh'.
Updated `terminfo.mdh'.
Updated `cap.mdh'.
Updated `clone.mdh'.
Updated `datetime.mdh'.
Updated `example.mdh'.
Updated `files.mdh'.
Updated `langinfo.mdh'.
Updated `mapfile.mdh'.
Updated `mathfunc.mdh'.
Updated `parameter.mdh'.
Updated `pcre.mdh'.
Updated `socket.mdh'.
Updated `stat.mdh'.
Updated `system.mdh'.
Updated `tcp.mdh'.
Updated `zftp.mdh'.
Updated `zprof.mdh'.
Updated `zpty.mdh'.
Updated `zselect.mdh'.
Updated `zle.mdh'.
Updated `complete.mdh'.
Updated `zutil.mdh'.
Updated `rlimits.mdh'.
Updated `sched.mdh'.
Updated `compctl.mdh'.
Updated `complist.mdh'.
Updated `computil.mdh'.
Updated `deltochar.mdh'.
Updated `zleparameter.mdh'.
        rm -f stamp-modobjs.tmp
Updated `zsh.mdh'.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o builtin.o builtin.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o compat.o compat.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o cond.o cond.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o exec.o exec.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o glob.o glob.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o hashtable.o hashtable.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
"/usr/include/rpcsvc/ypclnt.h", line 99.31: 1506-310 (I) The type "struct dom_binding" was introduced in a parameter list, and will go out of scope at the end of the function declaration or definition.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o hist.o hist.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
`zshpaths.h' is up to date.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o init.o init.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
    1265  1500-010: (W) WARNING in zsh_main: Infinite loop.  Program may not stop.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o input.o input.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
        /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o jobs.o jobs.c
"sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the end of line.
"signames.epro", line 5.74: 1506-186 (W) String literal must be ended before the end of line.
"jobs.c", line 686.43: 1506-276 (S) Syntax error: possible missing ')'?
"jobs.c", line 697.46: 1506-068 (S) Operation between types "char*" and "int" is not allowed.
"jobs.c", line 698.21: 1506-277 (S) Syntax error: possible missing ')' or ','?
"jobs.c", line 698.27: 1506-275 (S) Unexpected text ')' encountered.
"jobs.c", line 769.77: 1506-276 (S) Syntax error: possible missing ')'?
"jobs.c", line 773.88: 1506-277 (S) Syntax error: possible missing ')' or ','?
"jobs.c", line 775.77: 1506-277 (S) Syntax error: possible missing ')' or ','?
make: The error code from the last command is 1.


Stop.
make: The error code from the last command is 2.


Stop.
make: The error code from the last command is 1.


Stop.

[--- build zsh on AIX 5.2 ---]

Cheers,

			--ibraheem

Re: 4.2.0-pre-1

[Peter Stephenson]

Ibraheem Umaru-Mohammed wrote:
> "sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the
>  end of line.
> "signames.epro", line 5.74: 1506-186 (W) String literal must be ended before 
> the end of line.
>         /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o jobs.o 
> jobs.c
> "sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the
>  end of line.
> "signames.epro", line 5.74: 1506-186 (W) String literal must be ended before 
> the end of line.
> "jobs.c", line 686.43: 1506-276 (S) Syntax error: possible missing ')'?
> "jobs.c", line 697.46: 1506-068 (S) Operation between types "char*" and "int"
>  is not allowed.
> "jobs.c", line 698.21: 1506-277 (S) Syntax error: possible missing ')' or ','
> ?
> "jobs.c", line 698.27: 1506-275 (S) Unexpected text ')' encountered.
> "jobs.c", line 769.77: 1506-276 (S) Syntax error: possible missing ')'?
> "jobs.c", line 773.88: 1506-277 (S) Syntax error: possible missing ')' or ','
> ?
> "jobs.c", line 775.77: 1506-277 (S) Syntax error: possible missing ')' or ','
> ?

It seems to be falling over on the sigmsg(...) macros.

You should have a file in the Src directory where you are building
called sigcount.h containing something like

#define SIGCOUNT	45
#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal")

Is your version similar?  If so, is there something weird in the file
signames.c in the same directory (feel free to send to the file)?

Thanks for the info.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: 4.2.0-pre-1

[Ibraheem Umaru-Mohammed]

On [02/03/04 11:15 +0000], Peter Stephenson wrote:
> Ibraheem Umaru-Mohammed wrote:
> > "sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the
> >  end of line.
> > "signames.epro", line 5.74: 1506-186 (W) String literal must be ended before 
> > the end of line.
> >         /usr/vac/bin/cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o jobs.o 
> > jobs.c
> > "sigcount.h", line 2.74: 1506-186 (W) String literal must be ended before the
> >  end of line.
> > "signames.epro", line 5.74: 1506-186 (W) String literal must be ended before 
> > the end of line.
> > "jobs.c", line 686.43: 1506-276 (S) Syntax error: possible missing ')'?
> > "jobs.c", line 697.46: 1506-068 (S) Operation between types "char*" and "int"
> >  is not allowed.
> > "jobs.c", line 698.21: 1506-277 (S) Syntax error: possible missing ')' or ','
> > ?
> > "jobs.c", line 698.27: 1506-275 (S) Unexpected text ')' encountered.
> > "jobs.c", line 769.77: 1506-276 (S) Syntax error: possible missing ')'?
> > "jobs.c", line 773.88: 1506-277 (S) Syntax error: possible missing ')' or ','
> > ?
> > "jobs.c", line 775.77: 1506-277 (S) Syntax error: possible missing ')' or ','
> > ?
> 
> It seems to be falling over on the sigmsg(...) macros.
> 
> You should have a file in the Src directory where you are building
> called sigcount.h containing something like
> 
> #define SIGCOUNT	45
> #define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal")
> 
> Is your version similar?  If so, is there something weird in the file
> signames.c in the same directory (feel free to send to the file)?
> 
> Thanks for the info.
> 

Hmmmn, sigcount.h seems to have unclosed quotes:

,---- [ sigcount.h ]
| #define SIGCOUNT        59
| #define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal3)
`----

Any utility version you want me to test for? awk? sed? A regular expression
issue?

Cheers,

			--ibraheem

-- 

Re: 4.2.0-pre-1

[Peter Stephenson]

Ibraheem Umaru-Mohammed wrote:
> Hmmmn, sigcount.h seems to have unclosed quotes:
> 
> ,---- [ sigcount.h ]
> | #define SIGCOUNT        59
> | #define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal3)
> `----

Yes, I can believe that's wrong...  Presumably it's also wrong in
signames.c.

The problem must be in signames2.awk which generates this:

    printf "#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : %c%s%c)", 34, "unknown signal", 34

My guess is your awk is truncating the input line in some weird way.
(It can't be 80 characters, however, since you wouldn't get the `unknown
signal' at all.)  Can you try altering that line as per the following
patch and see if that helps?

If your awk is playing up, you might find other weirdness, in particular
the `# ifdef USE_SUSPENDED' bit in signames.c.  So even if it looks like
it works it would be worth checking (or posting) the resulting signames.c.
Any fixes ought to be similarly trivial, but I wouldn't like to second
guess what awk is actually getting up to.

Index: Src/signames2.awk
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/signames2.awk,v
retrieving revision 1.1.1.4
diff -u -r1.1.1.4 signames2.awk
--- Src/signames2.awk	15 Feb 2000 16:44:54 -0000	1.1.1.4
+++ Src/signames2.awk	2 Mar 2004 12:05:38 -0000
@@ -63,7 +63,8 @@
     printf "#include %czsh.mdh%c\n", 34, 34
     printf "\n"
     printf "/**/\n"
-    printf "#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : %c%s%c)", 34, "unknown signal", 34
+    printf "#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig]"
+    printf " : %c%s%c)", 34, "unknown signal", 34
     printf "\n"
     printf "/**/\n"
     printf "mod_export char *sig_msg[SIGCOUNT+2] = {\n"

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: 4.2.0-pre-1

[Ibraheem Umaru-Mohammed]

On [02/03/04 12:14 +0000], Peter Stephenson wrote:
> Ibraheem Umaru-Mohammed wrote:
> > Hmmmn, sigcount.h seems to have unclosed quotes:
> > 
> > ,---- [ sigcount.h ]
> > | #define SIGCOUNT        59
> > | #define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal3)
> > `----
> 
> Yes, I can believe that's wrong...  Presumably it's also wrong in
> signames.c.
> 
> The problem must be in signames2.awk which generates this:
> 
>     printf "#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : %c%s%c)", 34, "unknown signal", 34
> 
> My guess is your awk is truncating the input line in some weird way.
> (It can't be 80 characters, however, since you wouldn't get the `unknown
> signal' at all.)  Can you try altering that line as per the following
> patch and see if that helps?
> 
> If your awk is playing up, you might find other weirdness, in particular
> the `# ifdef USE_SUSPENDED' bit in signames.c.  So even if it looks like
> it works it would be worth checking (or posting) the resulting signames.c.
> Any fixes ought to be similarly trivial, but I wouldn't like to second
> guess what awk is actually getting up to.
> 
[...]

I think I've found what the problem is, but have no idea why it is happening.
Take a look at the following:

Linux:

	[ibraheem@sonic:~ ] 42 % uname -a
	Linux sonic 2.6.3-rc2-gentoo #2 SMP Wed Feb 18 09:12:33 GMT 2004 i686
	Pentium III (Coppermine) GenuineIntel GNU/Linux
	[ibraheem@sonic:~ ] 43 %  nawk 'BEGIN {printf "\n\n#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : %c%s%c)\n", 34, "unknown signal", 34}'


	#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown
	signal")
	[ibraheem@sonic:~ ] 44 %

AIX 4.3:
	
	[ibraheem@maserati:~ ] 45 % uname -a
	AIX maserati 3 4 0043CDDA4C00
	[ibraheem@maserati:~ ] 46 % nawk 'BEGIN {printf "\n\n#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : %c%s%c)\n", 34, "unknown signal", 34}'


	#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal")
	[ibraheem@maserati:~ ] 47 %

AIX 5.2

	ibraheem@md000002s:~ ] 48 % uname -a
	AIX md000002s 2 5 00541F5A4C00
	ibraheem@md000002s:~ ] 49 % nawk 'BEGIN {printf "\n\n#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : %c%s%c)\n", 34, "unknown signal", 34}'


	#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal3)
	ibraheem@md000002s: ~] 50 % 

However, it appears that /bin/nawk is the same as /bin/awk, and not a symlink as it should be.
I will attempt to compile up nawk, and use that. 

Cheers,

			--ibraheem.

-- 

Re: 4.2.0-pre-1

[Clint Adams]

> I have uploaded zsh 4.2.0-pre-1 to ftp.zsh.org.  (Should probably be in
> the development directory but isn't.)

Is there going to be a 4.1.2?

Re: 4.2.0-pre-1

[Peter Stephenson]

Clint Adams wrote:
> Is there going to be a 4.1.2?

No, we're going straight to 4.2.0.  In practice it's been stable for a
while now.  (It was never really that unstable.)

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: 4.2.0-pre-1

[Bart Schaefer]

On Feb 26,  7:17pm, Peter Stephenson wrote:
}
} Clint Adams wrote:
} > Is there going to be a 4.1.2?
} 
} No, we're going straight to 4.2.0.  In practice it's been stable for a
} while now.

There is the bug report in zsh-workers/19419, which it would be good to
address.