From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Angelo Graziosi Newsgroups: gmane.emacs.devel Subject: Re: Build failure for Emacs master Date: Tue, 12 Apr 2016 02:36:23 +0200 Message-ID: <570C4307.6050907@alice.it> References: <56CCD91E.6070507@alice.it> <83egc2ixji.fsf@gnu.org> <56CD798D.7060102@alice.it> <56CD8408.1000701@alice.it> <83wppuggb4.fsf@gnu.org> <56CE2CA7.5050906@alice.it> <83io1cg2pt.fsf@gnu.org> <56DA0327.2030009@alice.it> <83oaatxu72.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1460421423 20770 80.91.229.3 (12 Apr 2016 00:37:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Apr 2016 00:37:03 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 12 02:36:54 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1apmK5-0000Xw-J1 for ged-emacs-devel@m.gmane.org; Tue, 12 Apr 2016 02:36:53 +0200 Original-Received: from localhost ([::1]:37662 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apmK5-0003eb-02 for ged-emacs-devel@m.gmane.org; Mon, 11 Apr 2016 20:36:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35831) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apmJp-0003be-He for emacs-devel@gnu.org; Mon, 11 Apr 2016 20:36:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1apmJk-0003mV-Ga for emacs-devel@gnu.org; Mon, 11 Apr 2016 20:36:37 -0400 Original-Received: from smtp202.alice.it ([82.57.200.98]:23683) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apmJk-0003lK-5H; Mon, 11 Apr 2016 20:36:32 -0400 Original-Received: from [192.168.1.101] (79.19.227.36) by smtp202.alice.it (8.6.060.43) (authenticated as angelo.graziosi@alice.it) id 5697B30A18C5635B; Tue, 12 Apr 2016 02:36:29 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 In-Reply-To: <83oaatxu72.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 82.57.200.98 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:202856 Archived-At: Just for the record... After about a month, the issue has reappeared. Now it fails with this message: [...] Loading button... Loading loaddefs.el (source)... Wrong number of arguments: autoload, 1325 Makefile:540: set di istruzioni per l'obiettivo "emacs.exe" non riuscito make[1]: *** [emacs.exe] Errore 127 make[1]: uscita dalla directory "/tmp/work/emacs-master/src" Makefile:398: set di istruzioni per l'obiettivo "src" non riuscito make: *** [src] Errore 2 but the lisp/loaddefs.el seems to have the same defects.. Ciao, Angelo. Il 05/03/2016 08:25, Eli Zaretskii ha scritto: >> From: Angelo Graziosi >> Date: Fri, 4 Mar 2016 22:50:31 +0100 >> >> $ cat ./src/emacs/lisp/loaddefs.el >> [...] >> (autoload 'xref-collect-matches "xref" "\ >> Collect matches for REGEXP inside FILES in DIR. >> FILES is a string with glob patterns separated by spaces. >> IGNORES is a list of glob patterns. >> >> \(fn REGEXP FILES DIR IGNORES)" nil nil) >> >> ;;;*** >> >> >> while for the others >> >> $ cat ./src/emacs/lisp/.../loaddefs.el >> [...] >> ;;;*** >> >> >> (provide 'loaddefs) >> ;; Local Variables: >> ;; version-control: never >> ;; no-byte-compile: t >> ;; no-update-autoloads: t >> ;; coding: utf-8 >> ;; End: >> ;;; loaddefs.el ends here >> >> >> Maybe just retrying builds.. > > Yes, this looks like the same problem. > > The challenge is to catch the instance when such a faulty loaddefs.el > is produced, and see what happens there. Ideas for how to do that are > welcome. > >> In any cases this kind of failures are rather recent. I have built >> master on MSYS2 for months without any failure and since, say, first >> decade of February they occur.. > > I've seen this first in last November. Not sure if it's the same > problem, but the symptoms are very similar. > > Are all of your builds full bootstraps in a fresh directory using a > freshly cloned repository? >