From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: phillip.lord@russet.org.uk (Phillip Lord) Newsgroups: gmane.emacs.devel Subject: Re: Build failure for Emacs master Date: Tue, 12 Apr 2016 12:36:32 +0100 Message-ID: <87k2k3t5xb.fsf@russet.org.uk> 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> <570C4307.6050907@alice.it> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1460461019 32710 80.91.229.3 (12 Apr 2016 11:36:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Apr 2016 11:36:59 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Angelo Graziosi Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 12 13:36:48 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 1apwcg-0002g7-99 for ged-emacs-devel@m.gmane.org; Tue, 12 Apr 2016 13:36:46 +0200 Original-Received: from localhost ([::1]:47559 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apwcf-00016Z-6x for ged-emacs-devel@m.gmane.org; Tue, 12 Apr 2016 07:36:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47235) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apwcb-00014M-9Y for emacs-devel@gnu.org; Tue, 12 Apr 2016 07:36:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1apwca-00042z-AS for emacs-devel@gnu.org; Tue, 12 Apr 2016 07:36:41 -0400 Original-Received: from cloud103.planethippo.com ([31.216.48.48]:45755) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apwcU-0003yE-Fi; Tue, 12 Apr 2016 07:36:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=russet.org.uk; s=default; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From; bh=OUlNJAAYCDPV5qqFg6YX3aofcgqJZN5LPLZzztqP2Uo=; b=RhxP5gFAhyZuGjbJfkkEMRFz4l Mim+G/BheL8gKq50B356K2bNnDvZSZjx6KhTlf8xLKXninHTRq0gH6zBZUx1c7A9sD0+Yw9yXNdJh uT72q7jOq8fFnjBp9HGoPwCBBzactz+plUErKMpCyFbLGd/hxO64AVB+Ftwiocl68qmWhd6fjWqFE zMtnssHC1y67x3bq0q2rU/UCbu+7RS93L9CAL78EGSuLS6bw2BVrkDKl7oprNrgd3Hcdb6bQmJU7A VMzCQztepQ11uzW0HPqlky1GRfK0arkFzlgXSF/00FmWWj9kDW+jrBjwR8BE056bFzNiCsQKwzv8S lwTGmVUg==; Original-Received: from cpc1-benw10-2-0-cust373.gate.cable.virginm.net ([77.98.219.118]:57648 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86_1) (envelope-from ) id 1apwcT-0032iE-K6; Tue, 12 Apr 2016 12:36:33 +0100 In-Reply-To: <570C4307.6050907@alice.it> (Angelo Graziosi's message of "Tue, 12 Apr 2016 02:36:23 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud103.planethippo.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - russet.org.uk X-Get-Message-Sender-Via: cloud103.planethippo.com: authenticated_id: phillip.lord@russet.org.uk X-Authenticated-Sender: cloud103.planethippo.com: phillip.lord@russet.org.uk X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 31.216.48.48 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:202861 Archived-At: Reappeared randomly, or reappeared consistently on every build? Phil Angelo Graziosi writes: > 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? >>