[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: $status is read-only for zsh

From: Ralf Wildenhues
Subject: Re: $status is read-only for zsh
Date: Sun, 16 Nov 2008 18:02:56 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

* Ralf Wildenhues wrote on Sun, Nov 16, 2008 at 05:55:56PM CET:
>       Do not use read-only variable $status.
>       * tests/ (AC_RUN_IFELSE): Use $estatus instead of
>       $status, for zsh.

I see lots more test failures with zsh like this:

+--- clean-state-env.before     Thu Nov 13 22:38:34 2008
++++ clean-state-env.after      Thu Nov 13 22:38:34 2008
+@@ -1,4 +1,4 @@
+ CONFIG_SHELL=/usr/local/bin/zsh
+@@ -86,7 +86,7 @@
+ ZSH_NAME=zsh
+ __MKLVL__=4
++argv=(X '$CC' -c '$CFLAGS' '$CPPFLAGS' 'conftest.$ac_ext' '>&5')
+ bindir='${exec_prefix}/bin'
+ cache_file=config.cache
+ datadir='${datarootdir}'
../../autoconf/tests/ exit code was 1, expected 0

And found this bit in the zsh manpage:
| In  sh and ksh compatibility modes the following parameters are
| not special and not initialized by the shell: ARGC, argv, cdpath,
| fignore, fpath, HISTCHARS, mailpath, MANPATH, manpath, path, prompt,
| PROMPT, PROMPT2, PROMPT3, PROMPT4, psvar, status, watch.

so it seems something recently changed that caused the testsuite either
to use zsh where it didn't before (ok I know what that would be), or to
not let zsh operate in compatibility mode (emulate sh).

Does that ring a bell?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]