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

Update of sr #110657 (project autoconf): Status: Wont Do => Done Open/Closed:Open => Closed ___ Follow-up Comment #12: [comment #11

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

Follow-up Comment #11, sr #110657 (project autoconf): [comment #10 comment #10:] > This patch works great, thanks :-) > Sorry, I misspoke. The patch actually fails to set the variable EGREP_TRADITIONAL (it only sets ac_cv_path_EGREP_TRADITIONAL), so all egrep checks later fail, just as if the

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

Follow-up Comment #10, sr #110657 (project autoconf): [comment #9 comment #9:] > [comment #8 comment #8:] [...] > > egrep '(-z)' > That won't work if the pattern contains back-references, since it'll mess up the numbering. Indeed, forgot about that. > However, we can prepend '.?' to the

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

Follow-up Comment #9, sr #110657 (project autoconf): [comment #8 comment #8:] > there is another way than -e to escape that dash: simply put a pair of parenthesis around the search string: > > egrep '(-z)'

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

Follow-up Comment #8, sr #110657 (project autoconf): [comment #6 comment #6:] > How about the attached patch instead? Unfortunately, this patch doesn't work ... due to another peculiarity of UnixPC's egrep which had escaped earlier: for some weird reason, if -e is used, egrep doesn't support

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

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:

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

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

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

Follow-up Comment #5, sr #110657 (project autoconf): [comment #4 comment #4:] > For the record, despite this having been marked "won't do", I _would_ consider and review a patch (against current development trunk) that would make configure scripgs set $EGREP and $GREP to `egrep` on systems where

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

A related data point: the grep and egrep supplied with SunOS 4.1.1_U1 (which IIRC is somewhere between 4.2 and 4.3 BSD) both accept -e. However, if -e is specified more than once, they appear to use only the last occurrence. (I had expected that egrep, at least, would report all input lines that

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

Update of sr #110657 (project autoconf): Priority: 3 - Low => 1 - Later ___ Reply to this item at:

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

Follow-up Comment #4, sr #110657 (project autoconf): For the record, despite this having been marked "won't do", I _would_ consider and review a patch (against current development trunk) that would make configure scripgs set $EGREP and $GREP to `egrep` on systems where `egrep -e` works but `grep

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

Update of sr #110657 (project autoconf): Status: Need Info => Wont Do ___ Follow-up Comment #3: OK, I think I see what's happening now; you have an egrep that's good enough, but you also

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

Follow-up Comment #2, sr #110657 (project autoconf): >> For example, grep does not support -e , but egrep does. > AC_PROG_GREP looks for a grep that does support -e, so a configure script that uses that should have a $GREP that works, assuming you have one somewhere in your $PATH. (If not, you'll

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

Update of sr #110657 (project autoconf): Priority: 5 - Normal => 3 - Low Status:None => Need Info ___ Follow-up Comment #1: > For example,

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

URL: Summary: Autoconf configure script considers absence of usable grep a fatal error, although it only uses egrep thereafter Project: Autoconf Submitted by: alainknaff Submitted on: Sun 15 May