From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 10 00:58:22 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A23C106566B for ; Mon, 10 Mar 2008 00:58:22 +0000 (UTC) (envelope-from mbsd@pacbell.net) Received: from nlpi001.prodigy.net (nlpi001.sbcis.sbc.com [207.115.36.30]) by mx1.freebsd.org (Postfix) with ESMTP id 398D18FC16 for ; Mon, 10 Mar 2008 00:58:21 +0000 (UTC) (envelope-from mbsd@pacbell.net) X-ORBL: [69.236.76.168] Received: from antec (adsl-69-236-76-168.dsl.pltn13.pacbell.net [69.236.76.168]) by nlpi001.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id m2A0fFjb024386; Sun, 9 Mar 2008 19:41:15 -0500 Date: Sun, 9 Mar 2008 17:41:15 -0700 (PDT) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= To: Mike Meyer In-Reply-To: <20080309194050.39bab925@bhuda.mired.org> Message-ID: <20080309173523.D907@antec.home> References: <20080309152712.42752293@bhuda.mired.org> <47D46127.2030802@chuckr.org> <20080309194050.39bab925@bhuda.mired.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Why doesn't autoconf like our /bin/sh? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Mar 2008 00:58:22 -0000 On Sun, 9 Mar 2008, Mike Meyer wrote: [...] > So there are at *least* three things that could be considered broken, > in that changing them would fix the problem I encountered. > > 1) Our /bin/sh isn't classified as Definitely usable. > 2) zsh is Not usable. > 3) zsh is classified as Maybe usable. > > #1 could be fixed on our side, if we understood why it wasn't > usable. It could also be fixed by the autoconf folks. #2 has to be > fixed by the zsh folks. #3 has to be fixed by the autoconf folks. Zsh has a large number of configuration settings that can make it more or less sh(1)-compatible. I've been bitten by SH_WORD_SPLIT, which defaults to being incompatible, IIRC. Since zsh is my interactive shell of preference, I spent a few minutes trying to reproduce your problems, but failed. Perhaps there is something in your .z* config files that make things go awry? $.02, /Mikko