[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: grep-3.5 released [stable]
From: |
Paul Eggert |
Subject: |
Re: grep-3.5 released [stable] |
Date: |
Tue, 6 Oct 2020 11:47:57 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
On 10/5/20 6:03 PM, Dennis Clarke wrote:
alpha$ SHELL=/bin/bash bash -x configure CC=cc > configure.log 2>&1
alpha$ wc -l configure.log
11372 configure.log
alpha$
alpha$ grep -n 'ac_compiler_gnu' configure.log
2750:+ ac_compiler_gnu=
3268:+ eval 'ac_val=$ac_compiler_gnu'
That doesn't look right. There should be many instances of 'ac_compiler_gnu=' in
configure.log.
I just now took the latest grep snapshot I created
<https://www.cs.ucla.edu/~eggert/grep-3.5.8-b3eb.tar.gz>, and then ran this:
SHELL=/bin/bash bash -x configure CC=cc > configure.log 2>&1
It created a much-bigger configure.log:
$ wc -l configure.log
62148 configure.log
$ grep -n 'ac_compiler_gnu' configure.log
2609:+ ac_compiler_gnu=
2982:+ ac_compiler_gnu=
3258:+ ac_compiler_gnu=no
3368:+ ac_compiler_gnu=no
3901:+ ac_compiler_gnu=no
4036:+ ac_compiler_gnu=no
37960:+ eval 'ac_val=$ac_compiler_gnu'
50922:+ eval 'ac_val=$ac_compiler_gnu'
So there's something wrong with how 'configure' is running on your platform.
Perhaps you're using an old cache? If so, I suggest clearing it. Anyway, please
compare your configure.log with the one that I generated (I have attached a
compressed version). Or you can send the entire configure.log that you're
generating (preferably compressed).
Also, the ac_compiler_gnu= is not important with respect to GREP and EGREP; I
included that in my previous email only because it should be on the line just
before the lines that matter. The lines that matter in my previous email
<https://lists.gnu.org/r/grep-devel/2020-09/msg00125.html> are the lines that
start with "+ printf '%s\n' 'configure:6473: checking for grep that handles long
lines and -e'".
configure.log.gz
Description: application/gzip