> After that, I have tried to identify what was wrong. I found that in the
> configure script:
>
> --- configure.orig Sat Aug 26 18:20:16 2000
> +++ configure Sat Aug 26 18:20:39 2000
> @@ -1349,7 +1349,7 @@
> EOF
> ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
> { (eval echo configure:1352: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
> -ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
> +ac_err=`grep -vE '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
> if test -z "$ac_err"; then
> :
> else
>
> The line seems to be a regexp, right! Without the -E or egrep, it won't
> work on my system (my version of grep is: 2.4.2). Without this patch, the
> configure script found the ncurses lib but not the include files (from
> memory curses.h ncurses.h and curses/ncurses.h or something like that).
Then egrep should be used. -E is not a portable option for grep.
$ /bin/grep -E
/bin/grep: illegal option -- E
Usage: grep -hblcnsviw pattern file . . .
$
