On 5/10/2019 3:49 PM, Miro Kropáček wrote:
> Hi,
>
> I found this today by accident - it seems that grep's ./configure
> doesn't work with so called minimal bash (enabled in bash's configure
> via --enable-minimal-config).
>
> One can verify that not only by the failed ./configure process but
> als
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
Op 11-05-19 om 13:08 schreef Miro Kropáček:
It seems --enable-minimal-config isn't tested very often as both
4.3.48 and 4.2.x required a few #ifdef's to be added to make it
compile (Linux).
I think you're probably hitting this bug:
https://lists.gnu.org/archive/html/bug-bash/2016-09/msg00083.h
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
Op 12-05-19 om 13:40 schreef Miro Kropáček:
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 a
