GNU bug report logs - #17471
On Solaris 10, grep snapshot apparently hit by bleeding-edge Autoconf bug

Previous Next

Full log

View this message in rfc822 format

From: Eric Blake <eblake <at> redhat.com>
To: eggert <at> cs.ucla.edu, 17471 <at> debbugs.gnu.org
Cc: Autoconf bugs <bug-autoconf <at> gnu.org>
Subject: bug#17471: On Solaris 10, grep snapshot apparently hit by bleeding-edge Autoconf bug
Date: Mon, 12 May 2014 06:15:02 -0600

[Message part 1 (text/plain, inline)]

On 05/11/2014 02:48 PM, Paul Eggert wrote:
> Following up to the grep snapshot announcement in:
> 
> http://lists.gnu.org/archive/html/platform-testers/2014-05/msg00000.html
> 
> That snapshot failed to build the shell scripts egrep and fgrep properly
> on Solaris 10, because it set "SHELL = /bin/sh" in src/Makefile, which
> caused the makefile to put "#!/bin/sh" at the top of the shell scripts,
> which breaks because the shell scripts use a construct '${0%/*}' that
> Solaris 10 /bin/sh doesn't grok.  The build should have used SHELL =
> /bin/bash, which is what grep does with my test builds.

In autoconf.git, there are zero hits for:
git grep -F '0%/*'

However, in grep.git, there is:

src/egrep.sh:    if test -x "${0%/*}/@grep@"; then
src/egrep.sh:      PATH=${0%/*}:$PATH

The culprit is grep itself, not autoconf.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

[signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.