bug#35681: closed (grep's ./configure doesn't work with plain /bin/sh)

[GNU bug Tracking System]

Your message dated Thu, 2 Jan 2020 01:32:36 -0800
with message-id <address@hidden>
and subject line Re: grep's ./configure doesn't work with plain /bin/sh
has caused the debbugs.gnu.org bug report #35681,
regarding grep's ./configure doesn't work with plain /bin/sh
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
35681: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35681
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> grep's ./configure doesn't work with plain /bin/sh
>
>
>
>
> Date: 
>
> Sat, 11 May 2019 00:49:15 +0200
>
>
>
>
> 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 like:
>
> configure:3536: error: fn_grep: expected pattern
>
> Tested on the latest (3.3) version. If there are good reasons why
> ./configure needs full bash, I guess it shouldn't reference /bin/sh in
> that case.
>
> Cheers,
> Miro
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: grep's ./configure doesn't work with plain /bin/sh
>
>
>
>
> Date: 
>
> Thu, 2 Jan 2020 01:32:36 -0800
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
>
>
>
>
> As this was a bug (now fixed) in Bash not grep, I'm closing the grep bug report.
>
>
> --- End Message ---