[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#26274: 26.0.50; completion regression
From: |
Stephen Berman |
Subject: |
bug#26274: 26.0.50; completion regression |
Date: |
Wed, 29 Mar 2017 20:27:57 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
On Wed, 29 Mar 2017 13:28:18 -0400 Noam Postavsky
<npostavs@users.sourceforge.net> wrote:
> On Wed, Mar 29, 2017 at 1:00 PM, Stephen Berman <stephen.berman@gmx.net>
> wrote:
>>
>> This is commit a3207a383009720bbd89327425e0eb1c9c20c267. I have now
>> found an older build from master from February 8, commit
>> e3b659630843de7e459bce483c278af765c644f7, which does not have this
>> completion problem. However, when I run git bisect on these commits and
>> then make, it fails as follows:
>> [...]
>
> m4/count-leading-zeros.m4 is added by [1: 74f87fd], maybe try deleting
> aclocal.m4 to stop autoconf from trying to find it when building older
> commits? (although I would have thought autoreconf with the '-f' flag
> would be doing that already)
Thanks, removing that file allowed configure to complete, but now I get
this:
checking that generated files are newer than configure... done
configure: creating ./config.status
make: *** No rule to make target 'lib/gnulib.mk.in', needed by 'Makefile'.
Stop.
git bisect skip doesn't eliminate this failure.
On Wed, 29 Mar 2017 20:27:03 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Date: Wed, 29 Mar 2017 19:00:30 +0200
>>
>> >> March 15 and it also shows the problem). To reproduce:
>>
>> This is commit a3207a383009720bbd89327425e0eb1c9c20c267. I have now
>> found an older build from master from February 8, commit
>> e3b659630843de7e459bce483c278af765c644f7, which does not have this
>> completion problem.
>
> If so, then please see if the problematic commits are one or more of
> these:
>
> commit 9f9863e50298a3506165cc1f056ab3238f37cb9f
> Author: Michal Nazarewicz <mina86@mina86.com>
> AuthorDate: Fri Feb 17 16:36:44 2017 +0100
>
> Fix build failure caused by `Generate upcase and downcase tables from
> Unicod
>
> commit 6220faeb4e9be16b9dec728e72ea8dff2cfe35ba
> Author: Michal Nazarewicz <mina86@mina86.com>
> AuthorDate: Wed Sep 7 21:00:57 2016 +0200
>
> casing: don't assume letters are *either* upper- or lower-case
> (bug#24603)
>
> commit 5ec3a58462e99533ea5200de356302181d634d0b
> Author: Michal Nazarewicz <mina86@mina86.com>
> AuthorDate: Mon Sep 19 00:23:40 2016 +0200
>
> Generate upcase and downcase tables from Unicode data (bug#24603)
My guess is the first of these, since it's between the bad and good
builds; the other two commits are much earlier. But given the above
make failure, I don't know how to build that commit (or the one before
it).
Steve Berman
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/27
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/27
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/29
- bug#26274: 26.0.50; completion regression, Noam Postavsky, 2017/03/29
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/29
- bug#26274: 26.0.50; completion regression, Eli Zaretskii, 2017/03/29
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/30