As this was a bug (now fixed) in Bash not grep, I'm closing the grep bug report.
On 5/12/19 4:14 AM, L A Walsh wrote:
> Is it documented somewhere that bash's minimal config is POSIX compliant?
No. It's not. You need to add aliases to get basic compliance, then job
control and readline/history for the User Portability Utilities option.
--
``The lyf so short, the craft so
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
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
>
However configure works without bash around.
What you tested was bash's configure. The original
query was about grep's configure.
oops
dc
Hi.
Dennis Clarke wrote:
> On 5/10/19 6:49 PM, Miro Kropek 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
On 5/10/19 6: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
also by content
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
also by content of config.log - there are several messages
