> > "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
>
> Tim> Something like this, perhaps?
>
> For sure!
>
OK - installed (this may be resolved in bash 2.06; if so, I'll try to
remember to amend this entry accordingly).
___
Libtool mailing l
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
Tim> Something like this, perhaps?
For sure!
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
Something like this, perhaps?
2001-10-21 Tim Van Holder <[EMAIL PROTECTED]>
* doc/autoconf.texi: Mention the issue of bash 2.05's
`set' builtin.
Index: doc/autoconf.texi
===
RCS file: /cvs/autoconf/doc/autoconf.te
> >> > it is probably still worth mentioning in the autoconf manual's
> >> > section on portable shell programming.
> >>
> >> Yes, that makes sense.
>
> Tim> I'll whip up something tomorrow.
>
> Hi Tim! ;)
Hi Akim!
As you well know, time is a relative concept (in fact, to me it's
yesterday at
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
>> > it is probably still worth mentioning in the autoconf manual's
>> > section on portable shell programming.
>>
>> Yes, that makes sense.
Tim> I'll whip up something tomorrow.
Hi Tim! ;)
> Why is this broken?
I was only relaying a problem someone else reported; it seemed odd
to me, but without 2.05 lying around, I couldn't test it.
> 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
> From: "Tim Van Holder" <[EMAIL PROTECTED]>
> 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'
