This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: Potential bash 2.05 issues with 'set'
- To: tim dot van dot holder at pandora dot be
- Subject: Re: Potential bash 2.05 issues with 'set'
- From: Paul Eggert <eggert at twinsun dot com>
- Date: Fri, 21 Sep 2001 13:37:45 -0700 (PDT)
- CC: autoconf at gnu dot org, automake at gnu dot org, libtool at gnu dot org
- List-Id: Discussion list for automake <automake.gnu.org>
- References: <000301c142bc$b736eec0$9a8ce0d5@pandora.be>
> From: "Tim Van Holder" <tim.van.holder@pandora.be>
> Date: Fri, 21 Sep 2001 18:44:43 +0200
>
> bash's behaviour with regards to the 'set' builtin has changed in 2.05....
> This apparently lead to a broken config.cache when using bash 2.05....
> > ! ac_cv_path_install=${ac_cv_path_install='ginstall -c'}
> > --- 115 ----
> > ! ac_cv_path_install=${ac_cv_path_install=$'ginstall -c'}
Why is this broken? The two lines have the same behavior with Bash 2.05.
It's true that you can't parse the latter line with other shells.
So perhaps what you're saying is that, if you use Bash 2.05 to
run 'configure', you're stuck with using Bash 2.05 to do everything
else, too?
> it is probably still worth mentioning in the autoconf manual's
> section on portable shell programming.
Yes, that makes sense.