GNU bug report logs - #15690
new snapshot available: grep-2.14.51-7a35

Previous Next

Package: grep;

Reported by: Jim Meyering <jim <at> meyering.net>

Date: Wed, 23 Oct 2013 05:13:01 UTC

Severity: normal

Tags: notabug

Done: Jim Meyering <jim <at> meyering.net>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 15690 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Jim Meyering <jim <at> meyering.net>, 15690 <at> debbugs.gnu.org
Cc: platform-testers <at> gnu.org
Subject: meyering grep-2.14.51-7a35 fails on Ubuntu 13.10 x86-64
Date: Wed, 23 Oct 2013 00:44:38 -0700
>   http://meyering.net/grep/grep-2.14.51-7a35.tar.xz

That snapshot fails "make check" on Ubuntu 13.10 x86-64.
However, when I generate a tarball from the same git source,
"make check" works for me.

I think I tracked this down to a discrepancy in the tools used
to build this snapshot.  But it's getting late so I hope someone
else can check this.

The snapshot fails because the three tests multibyte-white-space,
pcre-utf8, surrogate-pair all fail.  And they fail because
"printf '\x40'" prints "\x40" rather than "@".
And this happens because the tests are run with
/bin/sh, not /bin/bash; on Ubuntu /bin/sh is Dash
and Dash mishandles printf with '\x...'.  And this
happens because './configure' decides to make SHELL
/bin/sh rather than /bin/bash.  And I think *this*
happens because 'configure' was built with Autoconf
2.69.112-f181 rather than Autoconf 2.69 (this is
the Autoconf 2.69 shipped with Fedora 19).  The
respective 'configure' scripts are pretty hairy,
though, and I can't easily see why the meyering.net
snapshot went awry.




This bug report was last modified 11 years and 211 days ago.

Previous Next


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