From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Build failure for Emacs master
Date: Tue, 12 Apr 2016 22:54:43 +0200 [thread overview]
Message-ID: <570D6093.8010305@alice.it> (raw)
In-Reply-To: <87k2k3t5xb.fsf@russet.org.uk>
Il 12/04/2016 13:36, Phillip Lord ha scritto:
>
> Reappeared randomly, or reappeared consistently on every build?
I would say "periodically"..
I had this issue on March 5 but then I was able to build OB on March 12,
23, 24, 29 and April 03. Now it reappeared... sometimes it fails with
lisp/loaddefs.el and sometimes with other loaddefs. For example this
evening:
[...]
In toplevel form:
../../emacs/lisp/gnus/gnus-icalendar.el:359:1:Error: End of file during
parsing:
c:/msys64/tmp/mingw-w64-emacs-git/src/emacs/lisp/org/org-loaddefs.el
Makefile:282: set di istruzioni per l'obiettivo
"gnus/gnus-icalendar.elc" non riuscito
make[2]: *** [gnus/gnus-icalendar.elc] Errore 1
[...]
..and org/org-loaddefs.el seems to suffers the same issues of
lisp/loaddefs.el I already flagged..
BTW, I notice that current build logs have a lot of "garbage" like this:
[...]
C:/msys64/tmp/mingw-w64-emacs-git/src/emacs/lib-src/ntlib.c:110:15:
warning: format '%d' expects argument of type 'int', but argument 2 has
type 'DWORD {aka long unsigned int}' [-Wformat=]
printf ("Checking parent status failed: %d\n", GetLastError ());
[...]
and Emacs also shows a lot of ^M characters..
I think this garbage is related to the configure messages:
[...]
checking whether C compiler handles -W... yes
checking whether C compiler handles -Wabi... yes
checking whether C compiler handles -Waddress... yes
checking whether C compiler handles -Waggressive-loop-optimizations... yes
checking whether C compiler handles -Wall... yes
checking whether C compiler handles -Wattributes... yes
checking whether C compiler handles -Wbool-compare... yes
checking whether C compiler handles -Wbuiltin-macro-redefined... yes
[...]
Why enabling this by default? All this should be OFF by default and only
the maintainers which need it should enable it
Angelo
>
> Phil
>
> Angelo Graziosi <angelo.graziosi@alice.it> 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 <angelo.graziosi@alice.it>
>>>> 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?
>>>
next prev parent reply other threads:[~2016-04-12 20:54 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 22:11 Build failure for Emacs master Angelo Graziosi
2016-02-23 23:14 ` Paul Eggert
2016-02-24 0:23 ` Angelo Graziosi
2016-02-24 3:42 ` Eli Zaretskii
2016-02-24 9:36 ` Angelo Graziosi
2016-02-24 10:20 ` Angelo Graziosi
2016-02-24 17:37 ` Eli Zaretskii
2016-02-24 22:20 ` Angelo Graziosi
2016-02-25 16:43 ` Eli Zaretskii
2016-03-04 21:50 ` Angelo Graziosi
2016-03-05 7:25 ` Eli Zaretskii
2016-03-05 13:53 ` Angelo Graziosi
2016-03-05 20:59 ` Angelo Graziosi
2016-03-06 3:35 ` Eli Zaretskii
2016-03-06 16:55 ` Eli Zaretskii
2016-03-06 22:00 ` Angelo Graziosi
2016-03-06 17:37 ` Andy Moreton
2016-03-06 17:54 ` Eli Zaretskii
2016-04-12 0:36 ` Angelo Graziosi
2016-04-12 11:36 ` Phillip Lord
2016-04-12 20:54 ` Angelo Graziosi [this message]
2016-04-12 22:52 ` MS-Windows warnings (was build failure) " Paul Eggert
2016-04-12 23:36 ` Angelo Graziosi
2016-04-13 5:49 ` Yuri Khan
2016-04-13 15:26 ` Eli Zaretskii
2016-04-13 18:06 ` Paul Eggert
2016-04-13 19:16 ` Eli Zaretskii
2016-04-19 15:46 ` Davis Herring
2016-04-19 16:04 ` Eli Zaretskii
2016-04-19 19:19 ` Davis Herring
2016-04-12 15:28 ` Build failure " Eli Zaretskii
2016-04-12 21:00 ` Angelo Graziosi
2016-04-12 21:49 ` Andy Moreton
2016-04-13 2:37 ` Eli Zaretskii
2016-04-13 23:11 ` Andy Moreton
2016-04-14 7:32 ` Phillip Lord
2016-04-14 16:06 ` Paul Eggert
2016-04-14 16:19 ` Eli Zaretskii
2016-04-14 16:50 ` O_BINARY and emacs_open (was: Build failure for Emacs master) Paul Eggert
2016-04-15 11:08 ` Build failure for Emacs master Phillip Lord
2016-04-15 14:40 ` Eli Zaretskii
2016-04-18 19:08 ` Phillip Lord
2016-04-18 19:33 ` Eli Zaretskii
2016-04-18 20:05 ` Phillip Lord
2016-04-18 21:10 ` Paul Eggert
2016-04-20 8:18 ` Phillip Lord
2016-04-20 15:05 ` Eli Zaretskii
2016-04-20 16:55 ` Phillip Lord
2016-04-20 17:41 ` Eli Zaretskii
2016-04-20 17:59 ` Andy Moreton
2016-04-21 10:46 ` Phillip Lord
2016-04-14 16:35 ` Eli Zaretskii
2016-04-14 17:06 ` Andy Moreton
2016-04-14 17:48 ` Eli Zaretskii
2016-04-14 18:40 ` Andy Moreton
2016-04-14 19:31 ` Eli Zaretskii
2016-04-14 20:30 ` Andy Moreton
2016-04-15 7:29 ` Eli Zaretskii
2016-04-15 8:18 ` Andy Moreton
2016-04-15 14:38 ` Eli Zaretskii
2016-04-15 15:36 ` Andy Moreton
2016-04-18 8:31 ` Angelo Graziosi
2016-04-18 18:30 ` Eli Zaretskii
2016-04-18 23:48 ` Andy Moreton
2016-04-19 9:58 ` Angelo Graziosi
2016-04-19 14:39 ` Eli Zaretskii
2016-04-19 21:15 ` Angelo Graziosi
2016-04-19 21:18 ` Angelo Graziosi
2016-04-19 21:20 ` Angelo Graziosi
2016-04-20 0:26 ` Paul Eggert
2016-04-20 14:25 ` Angelo Graziosi
2016-04-12 22:42 ` Angelo Graziosi
2016-04-13 20:12 ` Angelo Graziosi
2016-04-13 21:32 ` Paul Eggert
2016-04-13 22:00 ` Angelo Graziosi
2016-04-14 1:31 ` Paul Eggert
2016-04-14 8:03 ` Angelo Graziosi
2016-04-14 15:30 ` Eli Zaretskii
2016-04-14 15:58 ` Building Emacs on MSYS2 (was: Build failure for Emacs master) Óscar Fuentes
2016-04-14 16:09 ` Building Emacs on MSYS2 Paul Eggert
2016-04-14 16:13 ` Óscar Fuentes
2016-04-14 16:21 ` Eli Zaretskii
2016-04-14 16:46 ` Óscar Fuentes
2016-04-14 17:26 ` Eli Zaretskii
2016-04-14 20:09 ` Óscar Fuentes
2016-04-15 15:03 ` Paul Eggert
2016-04-15 15:37 ` Óscar Fuentes
2016-04-15 17:30 ` Paul Eggert
2016-04-15 17:58 ` Óscar Fuentes
2016-04-15 19:15 ` Paul Eggert
2016-04-15 19:40 ` Óscar Fuentes
2016-04-15 20:03 ` Eli Zaretskii
2016-04-15 20:20 ` Óscar Fuentes
2016-04-15 20:49 ` Eli Zaretskii
2016-04-15 21:37 ` Stephen Leake
2016-04-15 22:11 ` Óscar Fuentes
2016-04-16 6:42 ` Eli Zaretskii
2016-04-17 21:46 ` Fixing imagemagick on W32 Stephen Leake
2016-04-18 2:28 ` Eli Zaretskii
2016-04-16 6:30 ` Building Emacs on MSYS2 Eli Zaretskii
2016-04-16 12:17 ` Stephen Leake
2016-04-16 12:40 ` Eli Zaretskii
2016-04-16 20:34 ` png in emacs 25 mingw64 Stephen Leake
2016-04-16 21:02 ` Stephen Leake
2016-04-17 2:46 ` Eli Zaretskii
2016-04-17 2:45 ` Eli Zaretskii
2016-04-18 12:32 ` Building Emacs on MSYS2 Phillip Lord
2016-04-15 19:42 ` Stefan Monnier
2016-04-15 20:17 ` Óscar Fuentes
2016-04-15 21:22 ` Stefan Monnier
2016-04-14 16:15 ` Building Emacs on MSYS2 (was: Build failure for Emacs master) Eli Zaretskii
2016-04-14 16:43 ` Building Emacs on MSYS2 Óscar Fuentes
2016-04-14 17:35 ` Eli Zaretskii
2016-04-14 16:36 ` Build failure for Emacs master Angelo Graziosi
2016-04-14 16:39 ` Paul Eggert
2016-04-14 1:38 ` Stefan Monnier
2016-04-14 2:04 ` John Wiegley
2016-04-14 14:41 ` Paul Eggert
2016-02-24 17:31 ` Eli Zaretskii
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=570D6093.8010305@alice.it \
--to=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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).