Re: new snapshot available: grep-3.4-almost.26-5419

[Bruce Dubbs]

On 9/18/20 11:53 AM, Bruce Dubbs wrote:
> On 9/18/20 8:51 AM, Jim Meyering wrote:
> > On Thu, Sep 17, 2020 at 10:22 PM Bruce Dubbs <bruce.dubbs@gmail.com> 
> > wrote:
> > > On 9/17/20 11:49 PM, Jim Meyering wrote:
> > ...
> > > >     https://meyering.net/grep/grep-3.4-almost.26-5419.tar.xz
> > >
> > > On a LinuxFromScratch system (LFS-10.0) make check gives:
> > >
> > >      GNU grep 3.4-almost.26-5419: tests/test-suite.log
> > > =======================================================
> >
> > Hi Bruce,
> > Thanks for testing.
> > Unfortunately, your testing environment appears to be fatally broken.
> >
> > > # TOTAL: 114
> > > # PASS:  0
> >
> > Not a single test passed!
> >
> > > # SKIP:  113
> >
> > > Where all the SKIPs say:
> > > backref: skipped test: failed to find an adequate shell
> >
> > Test infra detected that your version of bash is broken.
> > The testing harness requires a bourne shell with certain minimal 
> > capabilities.
> > That system's version of bash lacked enough to be rejected. The bash
> > 5.0.17 on a Fedora 32 system works fine for me.
>
> Well the system I have is good enough to build about 1000 various 
> packages, including grep-3.4, including all tests.
>
> Testsuite summary for GNU grep 3.4
> ============================================================================ 
>
> # TOTAL: 185
> # PASS:  179
> # SKIP:  6
> # XFAIL: 0
> # FAIL:  0
> # XPASS: 0
> # ERROR: 0
>
> I'll note that if I run 'src/grep --help' I get an immediate segfault.
>
> [ /tmp/grep-3.4-almost.26-5419 ]$ ldd src/grep
>          linux-vdso.so.1 (0x00007ffe7a7dd000)
>          libpcre.so.1 => /lib/libpcre.so.1 (0x00007fe369de2000)
>          libsigsegv.so.2 => /usr/lib/libsigsegv.so.2 (0x00007fe369ddc000)
>          libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fe369dc2000)
>          libc.so.6 => /lib/libc.so.6 (0x00007fe369bfc000)
>          /lib64/ld-linux-x86-64.so.2 (0x00007fe369e4d000)
>
> gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35, GNU C Library (GNU libc) 
> version 2.32.
>
> I'm not familiar enough with the test sequence to check why it thinks my 
> bash is not usable.  Can you tell me where this check is happening.
>
> It might be because I get:
>
> $ ./get-mb-cur-max
> $ echo $?
> 1

Just following up.

I re-extracted the tarball and ran ./configure && make && make check and 
everything seems OK:

Testsuite summary for GNU grep 3.4-almost.26-5419
============================================================================
# TOTAL: 114
# PASS:  106
# SKIP:  6
# XFAIL: 2
# FAIL:  0
# XPASS: 0
# ERROR: 0

 Testsuite summary for GNU grep 3.4-almost.26-5419
============================================================================
# TOTAL: 192
# PASS:  184
# SKIP:  8
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

Which appears to be normal for this system.

But if I run ./configure --prefix=/usr --bindir=/bin grep wants to link 
with /usr/lib/libsigsegv.so /usr/lib/libc.a instead of just -lsigsegv
In this later case, grep segfaults early.

If I remove /usr/lib/libc.a, everything is fine.  I do not know why 
configure wants to use a static libc if the destination libraries are 
specified.

Is this possibly a gnulib issue?

  -- Bruce