On Tue, Dec 14, 2004 at 05:33:26AM +0100, Enrico Weigelt wrote:
> It is of these macros which are doing regex test. My build system runs
> the GNU grep v. 2.4.1. A short look the grep --help exposes, that the
> -E option has to be passed when using extendet regex. Simply calling
> egrep does not work here. On another system, running newer grep (2.5.1)
> evrything is fine. So it seems gnu grep changed its behaviour when
> called as egrep - in general a very bad thing.
>
> The only clean solutions are:
>
> a) use the old semantics
> b) encapsulate the grep command (into a shell function) and first
> check which version to use
> c) define grep-2.5.x as an build-tool dependency, check if its really
> installed and working an spit out at least an warning if it doesnt.
>
> Again its an autoconf problem. More than just a bug.
Does this mean the following macro should appear somewhere in
httpd's configury?
-- Macro: AC_PROG_EGREP
Check whether `$GREP -E' works, or else search the user's `PATH'
for `egrep', and `gegrep', in that order, and set output variable
`EGREP' to the one that accepts the longest input lines.
Cheers,
Patrick
