Date: Mon, 10 Mar 2008 10:50:29 +1100 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Mike Meyer <mwm-keyword-freebsdhackers2.e313df@mired.org> Cc: hackers@freebsd.org Subject: Why doesn't autoconf like zsh? (was: Why doesn't autoconf like our /bin/sh?) Message-ID: <20080309235029.GD86378@dereel.lemis.com> In-Reply-To: <20080309152712.42752293@bhuda.mired.org> References: <20080309152712.42752293@bhuda.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sunday, 9 March 2008 at 15:27:12 -0400, Mike Meyer wrote: > I've stumbled on to an obscure problem with autoconf 2.61, and I'm not > sure quite what to do with it. I've already sent mail to the autoconf > folks, but I'd like to understand what's going on. > > The problem is that, on a FreeBSD system with only /bin/sh and the > ports zsh as installed shells, if you have SHELL set to zsh when > invoking the autoconf-generated configure script, the script produces > a broken Makefile. It doesn't generate an error, it just complains > that: > > ... > > Setting SHELL to /bin/sh, or unsetting it, also solves this. This is pretty clear that this is a zsh issue, either because of bugs in zsh or (more likely, I'd guess) in autoconf. Greg -- See complete headers for address and phone numbers. --pZs/OQEoSSbxGlYw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH1HdhIubykFB6QiMRAkA9AJ0fpcjcW0gCQpofBmxyoZjxzZFjZwCeO89k 4cQafn+PReoaSa5r7PLPmfQ= =QXnH -----END PGP SIGNATURE----- --pZs/OQEoSSbxGlYw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080309235029.GD86378>