|
From: | Paul Eggert |
Subject: | Re: grep-3.5 released [stable] |
Date: | Mon, 28 Sep 2020 12:50:37 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
On 9/28/20 8:19 AM, Dennis Clarke wrote:
On 9/28/20 4:08 AM, Paul Eggert wrote:'configure' automatically looks in /usr/xpg4/bin if none of the grep's found in the PATH suffice. /usr/bin/grep does not suffice.configure ( once I removed those offending lines checking for grep which I have in multiple flavours ) would report this neatly :
We can't remove the 'configure' lines checking for grep, since grep is busted on some platforms (including plain Solaris). If those 'configure' lines reject /usr/local/bin/grep and /usr/local/bin/egrep on your platform, we need to figure out why.
To do that, I suggest running this command on an unmodified grep 3.5 distribution: SHELL=/bin/bash bash -x configure CC=cc > configure.log 2>&1and looking in 'configure.log' for why your 'grep' failed. Attached is the relevant part of the output I get with PATH='/usr/bin:/usr/ccs/bin:/r/share1/src/developerstudio12.6/bin' on Solaris 10 sparc. How does it compare to yours?
config.log-excerpt
Description: Text document
[Prev in Thread] | Current Thread | [Next in Thread] |