[Top][All Lists]

[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 22:00:27 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

On Wed, 29 Mar 2017 14:49:42 -0400 Noam Postavsky <address@hidden> wrote:

> On Wed, Mar 29, 2017 at 2:27 PM, Stephen Berman <address@hidden> wrote:
>> 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.
> Starting from a fresh checkout like Eli suggested is the safest way,
> but I guess you should be able to get around this error by deleting
> 'Makefile', and regenerating it by running ./configure again.

Thanks, I went this route, and it worked (and still took almost an hour
to go through eight iterations).  Git bisect in fact pinpointed this

5ec3a58462e99533ea5200de356302181d634d0b is the first bad commit
commit 5ec3a58462e99533ea5200de356302181d634d0b
Author: Michal Nazarewicz <address@hidden>
Date:   Mon Sep 19 00:23:40 2016 +0200

    Generate upcase and downcase tables from Unicode data  (bug#24603)
    Use Unicode data to generate case tables instead of mostly repeating
    them in lisp code.  Do that in a way which maps ‘Dz’ (and similar)
    digraph to ‘dz’ when down- and ‘DZ’ when upcasing.
    https://debbugs.gnu.org/cgi/bugreport.cgi?msg=89;bug=24603 lists all
    changes to syntax table and case tables introduced by this commit.
    * lisp/international/characters.el: Remove case-pairs defined with
    explicit Lisp code and instead use Unicode character properties.
    * test/src/casefiddle-tests.el (casefiddle-tests--characters,
    casefiddle-tests-casing): Update test cases which are now working
    as they should.

(When Eli listed this as a candidate, I doubted it because of the date,
since my build from February 8 of this year does not have the problem.
I guess that date is not the commit date.  Confusing when looking at the
commit log.)

Steve Berman

reply via email to

[Prev in Thread] Current Thread [Next in Thread]