zsh-users
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Martijn Dekker <martijn@inlv.org>
Cc: zsh-users@zsh.org
Subject: Re: Zsh requires Bash? 2002 revisited
Date: Sun, 7 Jan 2018 08:10:42 +0000	[thread overview]
Message-ID: <20180107081042.GA17598@chaz.gmail.com> (raw)
In-Reply-To: <4e96813d-3762-da35-f681-2546c0265982__30442.5932620235$1515274776$gmane$org@inlv.org>

2018-01-06 22:21:36 +0100, Martijn Dekker:
> Op 06-01-18 om 21:36 schreef Jim:
> > As I said I was testing different shells, it was by chance that /bin/sh and
> > /bin/posh were
> > linked when I started the build.
> 
> You're right, autoconf scripts do not depend on bash and work fine on
> any reasonably compliant POSIX shell, including recent zsh versions.
> 
> However, posh is non-compliant, bug-ridden, unmaintained, generally
> broken, and should not be used. Your problem would be solved by deleting
> posh and using dash for /bin/sh instead.
[...]

FWIW, with sh as dash, if I remove bash and ksh, then the
configure fails with

./configure:13185: functions: attempt to set associative array to scalar

IOW, it seems configure tries to rerun itself as bash, ksh or
zsh whichever is available when running as dash, but not when
running as posh, possibly because it detects that it is already
a variant of ksh? I've not looked in much more details.

Given that autoconf spends a lot of effort working around bugs
in various shell implementations, I suspect the problem is
coming from zsh specific code.

-- 
Stephane


  parent reply	other threads:[~2018-01-07  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06 13:47 Jim
2018-01-06 17:23 ` Bart Schaefer
2018-01-06 20:36   ` Jim
2018-01-06 20:57     ` Bart Schaefer
2018-01-07 20:41       ` Jim
2018-01-06 21:21     ` Martijn Dekker
     [not found]     ` <4e96813d-3762-da35-f681-2546c0265982__30442.5932620235$1515274776$gmane$org@inlv.org>
2018-01-07  8:10       ` Stephane Chazelas [this message]
2018-01-07 20:40         ` Bart Schaefer
2018-01-07  8:48       ` Stephane Chazelas
2018-01-07 15:14         ` Stephane Chazelas

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=20180107081042.GA17598@chaz.gmail.com \
    --to=stephane.chazelas@gmail.com \
    --cc=martijn@inlv.org \
    --cc=zsh-users@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).