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-0
On Thu, Sep 8, 2016 at 7:20 PM, Paul Eggert 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 a
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 bef
On Tue, Feb 16, 2016 at 9:34 AM, Nelson H. F. Beebe 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
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:
