[sr #110657] Autoconf configure script considers absence of usable grep a fatal error, although it only uses egrep thereafter

[Paul Eggert]

Follow-up Comment #7, sr #110657 (project autoconf):

[comment #6 comment #6:]
> How about the attached patch instead?
Oops, that patch had a stray -E so I removed it. Revised patch attached.

(file #53277)

___

Additional Item Attachment:

File name: 0001-Fix-bug-AC_EGREP_CPP-with-leading-in-pattern.patch Size:3 KB
   




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[sr #110657] Autoconf configure script considers absence of usable grep a fatal error, although it only uses egrep thereafter

[Paul Eggert]

Follow-up Comment #6, sr #110657 (project autoconf):

[comment #5 comment #5:]
> the only reason why AC_PROG_EGREP is brought in (in my case) is due to the
macro AC_EGREP_CPP, which does not ever use the -e option
AC_EGREP_CPP should use -e though, since it should work even if the pattern
begins with '-'.

How about the attached patch instead? It fixes that bug with '-', it defines a
new macro _AC_PROG_EGREP_TRADITIONAL which I hopes works as well on the AT
UnixPC as it does on today's platforms, and it avoids messing with
AC_PROG_EGREP due to the usual worries about breaking old stuff. This macro
name begins with underscore so it's private (I don't want users relying on
it).

> So this should also work on platforms were egrep doesn't support -e either.
We don't know of any such platforms so it should be OK to not worry about
that.


(file #53276)

___

Additional Item Attachment:

File name: 0001-Fix-bug-AC_EGREP_CPP-with-leading-in-pattern.patch Size:3 KB
   




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/