unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26274@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#26274: 26.0.50; completion regression
Date: Wed, 29 Mar 2017 20:27:57 +0200	[thread overview]
Message-ID: <87h92cym36.fsf@rosalinde> (raw)
In-Reply-To: <8337dw6ljs.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 29 Mar 2017 20:27:03 +0300")

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





  reply	other threads:[~2017-03-29 18:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 10:56 bug#26274: 26.0.50; completion regression Stephen Berman
2017-03-27 16:22 ` Stephen Berman
2017-03-29 17:00   ` Stephen Berman
2017-03-29 17:27     ` Eli Zaretskii
2017-03-29 18:27       ` Stephen Berman [this message]
2017-03-29 18:33         ` Eli Zaretskii
2017-03-29 18:43           ` Stephen Berman
2017-03-29 18:49         ` Noam Postavsky
2017-03-29 20:00           ` Stephen Berman
2017-03-30  2:33             ` Eli Zaretskii
2017-03-30 13:38               ` Michal Nazarewicz
2017-03-30 14:17                 ` Michal Nazarewicz
2017-03-30 14:30                   ` Michal Nazarewicz
2017-03-30 16:18                     ` Michal Nazarewicz
2017-03-30 18:02                       ` Stephen Berman
2017-03-30 19:11                         ` Michal Nazarewicz
2017-03-30 20:14                           ` Stephen Berman
2017-03-30 18:06                       ` Eli Zaretskii
2017-04-06 18:58                         ` Michal Nazarewicz
2017-04-07  8:37                           ` Stephen Berman
2017-03-29 17:28     ` Noam Postavsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h92cym36.fsf@rosalinde \
    --to=stephen.berman@gmx.net \
    --cc=26274@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).