From owner-freebsd-stable@FreeBSD.ORG Fri Mar 3 17:56:46 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77C1416A420; Fri, 3 Mar 2006 17:56:46 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: from n.0x5.de (n.0x5.de [217.197.85.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0FC743D45; Fri, 3 Mar 2006 17:56:45 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: by pc5.i.0x5.de (Postfix, from userid 1003) id 6D05881C33; Fri, 3 Mar 2006 18:56:44 +0100 (CET) Date: Fri, 3 Mar 2006 18:56:44 +0100 From: Nicolas Rachinsky To: freebsd-stable@FreeBSD.ORG Message-ID: <20060303175644.GA77766@mid.pc5.i.0x5.de> Mail-Followup-To: freebsd-stable@FreeBSD.ORG, obrien@FreeBSD.org References: <20060303172231.GA8478@xor.obsecurity.org> <20060303173355.1F0FB45041@ptavv.es.net> <20060303173925.GA8832@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060303173925.GA8832@xor.obsecurity.org> X-Powered-by: FreeBSD X-Homepage: http://www.rachinsky.de X-PGP-Keyid: 887BAE72 X-PGP-Fingerprint: 039E 9433 115F BC5F F88D 4524 5092 45C4 887B AE72 X-PGP-Keys: http://www.rachinsky.de/nicolas/gpg/nicolas_rachinsky.asc User-Agent: Mutt/1.5.11 Cc: obrien@FreeBSD.org Subject: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2006 17:56:46 -0000 * Kris Kennaway [2006-03-03 12:39 -0500]: > On Fri, Mar 03, 2006 at 09:33:55AM -0800, Kevin Oberman wrote: > > > > I hope someone has reported this error to the bash developers. > > > > If te latest bash version fixes the problem, it's a bit too late to > > report it. > > Well, how about testing the latest version to see if it's fixed? :-) Version 3.1.10 (which is the latest AFAIK) of the port contains the problem, at least here using FreeBSD 4.11. > Bottom line is: unless people take swift action about this it'll > probably stay broken in the release. I sent a report with bashbug and CCd the port maintainer. I can't test with other FreeBSD releases. Nicolas -- http://www.rachinsky.de/nicolas