[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Potential bash 2.05 issues with 'set'

From: Tim Van Holder
Subject: Re: Potential bash 2.05 issues with 'set'
Date: Sun, 21 Oct 2001 12:25:11 +0200

Something like this, perhaps?

2001-10-21  Tim Van Holder  <address@hidden>

        * doc/autoconf.texi: Mention the issue of bash 2.05's
        `set' builtin.

Index: doc/autoconf.texi
RCS file: /cvs/autoconf/doc/autoconf.texi,v
retrieving revision 1.552
diff -u -r1.552 autoconf.texi
--- doc/autoconf.texi   2001/10/20 06:56:45     1.552
+++ doc/autoconf.texi   2001/10/21 10:22:40
@@ -7504,6 +7504,15 @@
 Mode,, Bash @sc{posix} Mode, bash, The GNU Bash Reference Manual}, for

address@hidden Bash 2.05 and later
address@hidden Bash 2.05 and later
+Versions 2.05 and later of @command{bash} use a different format for
+output of the @command{set} builtin, designed to make evaluating this
+output easier.  However, this output is not compatible with earlier
+versions of @command{bash} (or with many other shells, probably).  So
+you use @command{bash} 2.05 or higher to execute @command{configure},
+you'll need to use @command{bash} 2.05 for all other build tasks as
 @item @command{/usr/xpg4/bin/sh} on Solaris
 @prindex @command{/usr/xpg4/bin/sh} on Solaris
 The @sc{posix}-compliant Bourne shell on a Solaris system is

reply via email to

[Prev in Thread] Current Thread [Next in Thread]