Re: Autoconf 2.53: improved fix for problems with CONFIG_SHELL=bash

[Aaron Ucko]

Paul Eggert <address@hidden> writes:

> > I'm against moving bash at the end.
> 
> Likewise, given that we seem to have more problems with ksh than bash
> in practice.

Fair enough.

> > So maybe we should just keep SHELL != CONFIG_SHELL.
> 
> Sorry, I don't understand this point.  I don't think Aaron Ucko was
> suggesting that we use the same variable for both concepts.

I initially made no suggestion about the relationship between these
variables.  However, part of the problem in this case is that
configure uses CONFIG_SHELL as a shell for things other than configure
and config.status, so limiting its role again would certainly help.

> Perhaps the installers had set BASH_ENV to point to their .bashrc?
> That might explain the problem.  There is a similar problem with ENV
> in various shells, including Bash in some cases.  Sounds a bit weird,
> though -- why would someone put a "cd" command in their BASH_ENV?

That's my suspicion as well.  I suppose it's reasonable to declare
their configuration too bogus to support.

> Anyway, If my guess is correct, the following untested patch should
> fix things.  But I would like some confirmation and advice before
> installing this.

Although that patch looks reasonable and seems quite likely to help,
it doesn't address all the current uses of CONFIG_SHELL; if you go
this route, it would probably be best to limit CONFIG_SHELL's role
again.