GNU bug report logs - #22702
[bug-grep] grep-2.23 build feedback

Previous Next

Package: grep;

Reported by: "Nelson H. F. Beebe" <beebe <at> math.utah.edu>

Date: Tue, 16 Feb 2016 17:52:02 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22702 in the body.
You can then email your comments to 22702 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-grep <at> gnu.org:
bug#22702; Package grep. (Tue, 16 Feb 2016 17:52:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Nelson H. F. Beebe" <beebe <at> math.utah.edu>:
New bug report received and forwarded. Copy sent to bug-grep <at> gnu.org. (Tue, 16 Feb 2016 17:52:02 GMT) Full text and rfc822 format available.

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

From: "Nelson H. F. Beebe" <beebe <at> math.utah.edu>
To: bug-grep <at> gnu.org
Cc: beebe <at> math.utah.edu
Subject: [bug-grep] grep-2.23 build feedback
Date: Tue, 16 Feb 2016 10:34:22 -0700
I've just been through a collection of build logs on more than 75
flavors of Unix for grep-2.23, and am pleased to report that all tests
passed on 46 of them.  Most of the others reported only 1 or 2
failures, but because the failures are similar across platforms, I
summarize them here:

FAIL:
	encoding-error
				x86		MirBSD 10

	fmbtest
				IA-64		GNU/Linux Red Hat 5.11
				x86		GNU/Linux CentOS 5.11
				x86-64		GNU/Linux CentOS 5.11

	invalid-multibyte-infloop
				x86		MirBSD 10

	multibyte-white-space
				x86		MirBSD 10
				x86-64		DragonFlyBSD 4.4, 4.6
				x86-64		FreeBSD 11
				x86-64		OpenIndiana 11

	pcre-infloop		x86-64		GNU/Linux Slackware 14

	pcre-invalid-utf8-input
				x86-64		GNU/Linux Debian 6
				x86-64		GNU/Linux Slackware 14

	pcre-jitstack
				PowerPC G4	MacOS X 10.5.8
				x86		Mac OS X 10.7.5
				x86		MirBSD 10
				x86		OpenBSD 4.9, 5.1
				x86-64		DragonFlyBSD 4.4, 4.6
				x86-64		KfreeBSD 7.7
				x86-64		NetBSD 5 and 6
				x86-64		OpenBSD 5.{4,5,6,7,8}

	surrogate-pair
				x86-64		OpenBSD 5.8

XFAIL:
	backref-alt
				IA-64		GNU/Linux Red Hat 5.11
				x86		GNU/Linux CentOS 5.11
				x86-64		GNU/Linux CentOS 5.11
				x86-64		KfreeBSD 7.7

	equiv-classes
				PowerPC G4	MacOS X 10.5.8
				x86		Mac OS X 10.7.5
				x86		MirBSD 10
				x86		OpenBSD 4.9, 5.1
				x86-64		DragonFlyBSD 4.4, 4.6
				x86-64		FreeBSD 11
				x86-64		GNU/Linux Debian 6
				x86-64		GNU/Linux Slackware 14
				x86-64		NetBSD 5 and 6
				x86-64		OpenBSD 5.{4,5,6,7,8}

	triple-backref
				IA-64		GNU/Linux Red Hat 5.11
				PowerPC G4	MacOS X 10.5.8
				x86		Mac OS X 10.7.5
				x86		MirBSD 10
				x86-64		DragonFlyBSD 4.4, 4.6
				x86-64		GNU/Linux CentOS 5.11
				x86-64		NetBSD 5 and 6
				x86-64		OpenBSD 5.{4,5,6,7,8}
				x86-64		OpenIndiana 11

Some of those failures may be related to deficient multibyte and UTF-8
support on some platforms; I wonder whether there might be a simple
one-line test that could check for such deficiencies and suppress the
rest of the test if so.  It would be nice if the tests could mostly
succeed everywhere, even if that means that some tests are suppressed
because of limited platform support.

In addition, compilation on MacOS X 10.10 (Yosemite) and 10.11 (El
Capitan) produces these warnings from clang masquerading as gcc:

	make[3]: Entering directory '/private/var/tmp/build/bare/grep-2.23/lib'
	Makefile:1684: target '.deps/alloca.Po' given more than once in the same rule
	  CC       argmatch.o

	  CC       error.o
	error.c:386:12: warning: data argument not used by format string [-Wformat-extra-args]
		   file_name, line_number);
		   ^
	1 warning generated.

	  CC       regex.o
	In file included from regex.c:70:
	./regex_internal.c:1392:11: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
	  if (idx < 0 || idx >= set->nelem)
	      ~~~ ^ ~
	1 warning generated.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe <at> math.utah.edu  -
- 155 S 1400 E RM 233                       beebe <at> acm.org  beebe <at> computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------




Information forwarded to bug-grep <at> gnu.org:
bug#22702; Package grep. (Thu, 18 Feb 2016 17:24:02 GMT) Full text and rfc822 format available.

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

From: Jim Meyering <jim <at> meyering.net>
To: "Nelson H. F. Beebe" <beebe <at> math.utah.edu>, automake-patches <at> gnu.org
Cc: 22702 <at> debbugs.gnu.org
Subject: Re: bug#22702: [bug-grep] grep-2.23 build feedback
Date: Thu, 18 Feb 2016 09:22:55 -0800
[Message part 1 (text/plain, inline)]
On Tue, Feb 16, 2016 at 9:34 AM, Nelson H. F. Beebe <beebe <at> math.utah.edu> wrote:
...
Thank you for all of the feedback.
I agree that many of the failures are due to inadequate library
support, and we should eventually improve the tests to detect
the inferior interfaces and diagnose them as such. However,
that is not on my short list, for now.

> In addition, compilation on MacOS X 10.10 (Yosemite) and 10.11 (El
> Capitan) produces these warnings from clang masquerading as gcc:
>
>         make[3]: Entering directory '/private/var/tmp/build/bare/grep-2.23/lib'
>         Makefile:1684: target '.deps/alloca.Po' given more than once in the same rule
>           CC       argmatch.o

I actually wrote a patch to fix the automake bug that led to this,
but did not find the time to write a stand-alone test case.
Today, I wrote the commit log entry and am attaching the
incomplete diff (no NEWS and no test) here, in case someone
wants to help move this along before I find time.
[0001-do-not-emit-rule-with-two-.deps-alloca.Po-dependents.patch (text/x-patch, attachment)]

Information forwarded to bug-grep <at> gnu.org:
bug#22702; Package grep. (Fri, 09 Sep 2016 02:21:02 GMT) Full text and rfc822 format available.

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Jim Meyering <jim <at> meyering.net>, "Nelson H. F. Beebe"
 <beebe <at> math.utah.edu>, automake-patches <at> gnu.org
Cc: 21815-done <at> debbugs.gnu.org, sur-behoffski <sur_behoffski <at> internode.on.net>,
 22702 <at> debbugs.gnu.org
Subject: Re: bug#22702: [bug-grep] grep-2.23 build feedback
Date: Thu, 8 Sep 2016 19:20:00 -0700
Jim Meyering wrote:
> I actually wrote a patch to fix the automake bug that led to this,
> but did not find the time to write a stand-alone test case.
> Today, I wrote the commit log entry and am attaching the
> incomplete diff (no NEWS and no test) here, in case someone
> wants to help move this along before I find time.

Thanks, I installed that patch into automake (Savannah micro branch).

This should fix Bug#21815 so I'll close that bug report while I'm at it.




Information forwarded to bug-grep <at> gnu.org:
bug#22702; Package grep. (Fri, 09 Sep 2016 03:15:01 GMT) Full text and rfc822 format available.

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

From: Jim Meyering <jim <at> meyering.net>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 21815-done <at> debbugs.gnu.org, 22702 <at> debbugs.gnu.org,
 sur-behoffski <sur_behoffski <at> internode.on.net>, automake-patches <at> gnu.org,
 "Nelson H. F. Beebe" <beebe <at> math.utah.edu>
Subject: Re: bug#22702: [bug-grep] grep-2.23 build feedback
Date: Thu, 8 Sep 2016 20:13:51 -0700
On Thu, Sep 8, 2016 at 7:20 PM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> Jim Meyering wrote:
>>
>> I actually wrote a patch to fix the automake bug that led to this,
>> but did not find the time to write a stand-alone test case.
>> Today, I wrote the commit log entry and am attaching the
>> incomplete diff (no NEWS and no test) here, in case someone
>> wants to help move this along before I find time.
>
> Thanks, I installed that patch into automake (Savannah micro branch).
>
> This should fix Bug#21815 so I'll close that bug report while I'm at it.

Thanks, Paul.




Reply sent to Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility. (Mon, 21 Sep 2020 19:39:02 GMT) Full text and rfc822 format available.

Notification sent to "Nelson H. F. Beebe" <beebe <at> math.utah.edu>:
bug acknowledged by developer. (Mon, 21 Sep 2020 19:39:02 GMT) Full text and rfc822 format available.

Message #19 received at 22702-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: "Nelson H. F. Beebe" <beebe <at> math.utah.edu>
Cc: 22702-done <at> debbugs.gnu.org
Subject: Re: bug#22702: [bug-grep] grep-2.23 build feedback
Date: Mon, 21 Sep 2020 12:38:47 -0700
On 9/8/16 7:20 PM, Paul Eggert wrote:

> This should fix Bug#21815 so I'll close that bug report while I'm at it.

Bug#22702 (build feedback for grep 2.23) has been superseded by Nelson H. F. 
Beebe's more recent build report for grep-3.4-almost.19-ff30:

https://lists.gnu.org/r/grep-devel/2020-09/msg00028.html

so I'm closing the circa-2016 bug report to tidy up things.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 20 Oct 2020 11:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 3 years and 187 days ago.

Previous Next


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