[Octave-bug-tracker] [bug #63174] New build warnings about egrep with grep 3.8

[Arun Giridhar]

Follow-up Comment #2, bug #63174 (project octave):

The problem is very silly. This is the new "egrep" in grep 3.8. They're
forcing the warning to stderr without changing the return value, so configure
scripts calling egrep don't realize there's something wrong and don't know
they should try something else:

$ cd /usr/bin/

$ cat egrep 
#!/bin/sh
cmd=${0##*/}
echo "$cmd: warning: $cmd is obsolescent; using grep -E" >&2
exec grep -E "$@"


I renamed egrep and fgrep in an attempt to get configure to recognize the real
grep:


$ sudo mv egrep egrep.old
$ sudo mv fgrep fgrep.old


Then I reran bootstrap, configure, and make. This time there were no errors
for Octave. There was one warning within gnulib itself because it used a
literal hardcoded "egrep" when searching for sed when running configure.

Alternatively: you can comment out that warning in egrep and fgrep. to restore
old behavior.

Either way, this is either a grep problem or a gnulib problem, and they broke
what was working before, but until one of them fixes it, the above two are
viable workarounds for building Octave.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63174>

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