building binutils : gnu grep

Riccardo Mottola rmottola at opencsw.org
Thu Apr 9 16:22:24 CEST 2015


Hi,

I tried building binutils 2.24 (current) on solaris 9 sparc and x86.

Build completes. However I see this:

mv -f .deps/eelf32lppclinux.Tpo .deps/eelf32lppclinux.Po
LIB_PATH='' /bin/bash ./genscripts.sh "." "/opt/csw/lib" "/opt/csw" 
"/opt/csw" i386-pc-solaris2.9 i386-pc-solaris2.9 i386-pc-solaris2.9 
"elf_i386_sol2 elf_i386_ldso elf_i386 elf_x86_64_sol2 elf_x86_64 
elf_l1om elf_k1om" "/usr/local/lib /usr/ccs/lib /lib /usr/lib" no yes 
elf32lppcnto ""
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
<..snip..>

This makes me doubt of the quality of the final product.

I suppose we need ggrep (gnu grep) here.
In the receipe I see this commented line:

# We need GNU grep
#PATH := /opt/csw/gnu:$(PATH)


Some other came to the same conclusion!

I don't see a configure parameter, but what tricks could be ther? I 
thought of GREP=/opt/csw/bin/ggrep

But where should I put that?

Riccardo


More information about the maintainers mailing list