Thanks for following up; sounds like grep is OK then, so closing the bug.
> >$ PATH=/usr/bin gegrep
> >grep: illegal option -- E
>
> On recently-patched Solaris 10 with bleeding-edge GNU grep, I see the
> following instead:
>
> $ PATH=/usr/bin gegrep
> gegrep: not found
>
> The above behavior is with /bin/sh, and with gegrep installed in some
> directory that is i
Vladimir Marek wrote:
$ PATH=/usr/bin gegrep
grep: illegal option -- E
On recently-patched Solaris 10 with bleeding-edge GNU grep, I see the following
instead:
$ PATH=/usr/bin gegrep
gegrep: not found
The above behavior is with /bin/sh, and with gegrep installed in some directory
that
Hi,
$ PATH=/usr/bin gegrep
grep: illegal option -- E
Usage: grep [-c|-l|-q] -bhinsvw pattern file . . .
The gegrep script:
#!/bin/bash
grep=grep
case $0 in
*/*)
dir=${0%/*}
if test -x "$dir/grep"; then
PATH=$dir:$PATH
grep=grep
fi;;
esac
exec $grep -E "$@"
The proble
