From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24674 invoked from network); 24 May 2000 03:56:27 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 24 May 2000 03:56:27 -0000 Received: (qmail 3699 invoked by alias); 24 May 2000 03:56:20 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11546 Received: (qmail 3692 invoked from network); 24 May 2000 03:56:19 -0000 From: "Bart Schaefer" Message-Id: <1000524035559.ZM1361@candle.brasslantern.com> Date: Wed, 24 May 2000 03:55:59 +0000 In-Reply-To: <200005240119.UAA16187@umgah.mesas.com> Comments: In reply to Chuck Hardin "configure script for zsh breaks for NetBSD /bin/sh, but not for NetBSD /bin/bash" (May 23, 8:19pm) References: <200005240119.UAA16187@umgah.mesas.com> X-Mailer: Z-Mail (5.0.0 30July97) To: Chuck Hardin , zsh-workers@sunsite.auc.dk Subject: Re: configure script for zsh breaks for NetBSD /bin/sh, but not for NetBSD /bin/bash MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 23, 8:19pm, Chuck Hardin wrote: } Subject: configure script for zsh breaks for NetBSD /bin/sh, but not for N } } The master configure script included in zsh v3.0.7 breaks on my NetBSD 1.4.1 } box at line 1356 with the message: } } ./configure: 1356: Syntax error: word unexpected (expecting ")") There's nothing special about that case statement and it parsed several far more complex ones near the top (e.g. the ones that parse the options passed to configure) without complaint. So I think that's a red herring. It's possible that this is a memory problem of some kind, e.g. that either a hard or soft system limit is being exceeded. The size of the environment, the size of the heap or stack, something like that. In fact, that's the only explanation I can think of. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com