From xemacs-m  Tue May 27 13:14:50 1997
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA06757
	for <xemacs-beta@xemacs.org>; Tue, 27 May 1997 13:14:49 -0500 (CDT)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.8.6.Beta3/8.8.6.Beta3) with ESMTP id OAA21356;
	Tue, 27 May 1997 14:14:42 -0400
Message-Id: <199705271814.OAA21356@black-ice.cc.vt.edu>
To: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Cc: xemacs-beta@xemacs.org
Subject: Re: AIX /bin/sh chokes on autoconf 2 configure script 
In-Reply-To: Your message of "27 May 1997 10:36:46 +0200."
             <y9llo51ia5d.fsf@modas.informatik.uni-tuebingen.de> 
From: Valdis.Kletnieks@vt.edu
X-Url: http://black-ice.cc.vt.edu/~valdis/
References: <199705262225.PAA10165@ringtail.nas.nasa.gov>
            <y9llo51ia5d.fsf@modas.informatik.uni-tuebingen.de>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_378684452P";
	micalg=pgp-md5; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 27 May 1997 14:14:42 -0400

--==_Exmh_378684452P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On 27 May 1997 10:36:46 +0200, you said:
> >>>>> "Lonhyn" =3D=3D Lonhyn T Jasinskyj <lonhyn@nas.nasa.gov> writes:
> =

> Lonhyn> Under AIX /bin/sh is not sh, it is ksh. If you really want sh t=
hen you
> Lonhyn> need to use /bin/bsh. I wasted about half a day discovering thi=
s one

This is not IBM's fault.  Apparently, POSIX compliance requires that /bin=
/sh
be a ksh-compliant shell.
 =

> I know, but that's not the point.  The point is that running
> ./configure chokes.  The question is whether to advise people on using =

> something else, or if the problem should be fixed.  Previous configure =

> scripts used to work fine with ksh.

If you're running AIX 4.1.4, I suggest that you apply the current set of
fixes to the shells (bos.rte.shell) - the current release is 4.1.4.23, an=
d
back around .11 or so, there were some fixes that corrected death I was
encountering in configure for some GNU-ish program  (it may have been
Perl, but I can't remember).  The exact problem was that the buggy ksh
would fail to fully expand things that looked like ${somevar$ext}.

I don't see any of these in the current Configure, so that might not be
your problem.

-- =

				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech



--==_Exmh_378684452P
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQCVAwUBM4skj9QBOOoptg9JAQH9sAP9EnvufS+b5sej435Hkhmy1M9/eLFsWWAE
ZSolnlO8mI/cx7RQBbdLi8wKvU8RW6GToHUFaO7gshX0dn92wS0+4sfMF06ZCSA0
Iik4kJxTZfGaMqHf3pL7UVHA4ccm/Ct9+AlcL9viyQxGzuxA1JQzxyXwIJAVsAt7
HpzdPpH+XYU=
=4oqj
-----END PGP MESSAGE-----

--==_Exmh_378684452P--

