On Tue, 14 May 2019 at 23:20, Chet Ramey wrote:
> That's similar to the report Martijn cited, but not the same. The right one is
>
> http://lists.gnu.org/archive/html/bug-bash/2016-11/msg00031.html
>
> and the right commit is
>
> http://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=78a3f8a
On Sun, 12 May 2019 at 21:32, Martijn Dekker wrote:
> Chet only commits snapshots to git and not individual fixes, so it's
> hard to isolate any one fix from the git repo.
Yes, I have noticed. :-)
> Are you sure? I just did a test compile on that same commit with
> '--enable-minimal-config --enab
On Sun, 12 May 2019 at 12:47, Martijn Dekker wrote:
> I think you're probably hitting this bug:
>
> https://lists.gnu.org/archive/html/bug-bash/2016-09/msg00083.html
Thanks, that indeed looks like it.
> The exit status of subshells is broken in bash-4.3 and bash-4.4 with
> --enable-minimal-config
On Sun, 12 May 2019 at 10:14, L A Walsh wrote:
> Is it documented somewhere that bash's minimal config is POSIX compliant?
> I'm not sure, off hand.
Not sure either. The docs say: "This produces a shell with minimal
features, close to the historical Bourne shell" and
https://www.gnu.org/software/b
On Sat, 11 May 2019 at 01:15, Miro Kropáček wrote:
> So it would seem it is something which broke between 2.05 and 4.4.23.
I had some time to test it more:
sh-4.4.23: doesn't work
sh-4.3.0: doesn't work
sh-4.3.48: doesn't work
sh-4.2.53: works
sh-4.1: works
sh-4.0: works
s
Hi,
I found this today by accident - it seems that grep's ./configure
doesn't work with the minimal bash (enabled in bash's configure
via --enable-minimal-config).
One can verify that not only by the failed ./configure process but
also by content of config.log - there are several messages like:
