From: Paul Eggert <eggert@cs.ucla.edu>
To: Kaushal Modi <kaushal.modi@gmail.com>,
Dmitry Gutov <dgutov@yandex.ru>,
Emacs developers <emacs-devel@gnu.org>,
Michael Albinus <michael.albinus@gmx.de>
Subject: Re: Recursive load? master build fail
Date: Sat, 7 May 2016 18:56:27 -0700 [thread overview]
Message-ID: <572E9CCB.7070401@cs.ucla.edu> (raw)
In-Reply-To: <CAFyQvY1HXLrTwKSw4+VGk6B2keUWKmwP4JrxX8ivU56PNtz5ew@mail.gmail.com>
Kaushal Modi wrote:
> On Sat, May 7, 2016, 9:22 PM Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
>> I also saw those recursive load errors when launching emacs after a quick
>> make and make install. So I tried doing a clean build using make bootstrap.
>> But then the build itself failed with the same recursive load errors.
>>
>
> @Michael I saw mentions of tramp.elc in the errors. Any idea if/how recent
> tramp.el changes could have caused this?
make -j5 bootstrap worked, if I recall correctly.
But I just now tried this in an already-built master on Ubuntu 16.04 x86-64:
cd lisp && make compile-always
and it failed:
ELC progmodes/js.elc
>>Error occurred processing progmodes/js.el: error (("Recursive load"
"/home/eggert/src/gnu/emacs/static-checking/lisp/net/tramp.elc"
"/home/eggert/src/gnu/emacs/static-checking/lisp/net/tramp.elc"
"/home/eggert/src/gnu/emacs/static-checking/lisp/net/tramp.elc"
"/home/eggert/src/gnu/emacs/static-checking/lisp/net/tramp.elc"
"/home/eggert/src/gnu/emacs/static-checking/lisp/net/tramp.elc"
"/home/eggert/src/gnu/emacs/static-checking/lisp/emacs-lisp/warnings.elc"))
Makefile:282: recipe for target 'progmodes/js.elc' failed
Then, when I did another 'make', it worked. So perhaps there's a race in there
somehow?
next prev parent reply other threads:[~2016-05-08 1:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 21:58 Recursive load? master build fail Kaushal Modi
2016-05-07 23:27 ` Dmitry Gutov
2016-05-08 0:08 ` Paul Eggert
2016-05-08 1:22 ` Kaushal Modi
2016-05-08 1:31 ` Kaushal Modi
2016-05-08 1:56 ` Paul Eggert [this message]
2016-05-08 7:17 ` Paul Eggert
2016-05-08 7:55 ` Michael Albinus
2016-05-08 9:50 ` Michael Albinus
2016-05-08 14:24 ` Kaushal Modi
2016-05-08 19:00 ` Colin Baxter
2016-05-11 5:22 ` Colin Baxter
2016-05-08 19:13 ` Paul Eggert
2016-05-08 22:06 ` Michael Albinus
2016-05-09 6:43 ` Paul Eggert
2016-05-09 7:23 ` Michael Albinus
2016-05-11 6:17 ` Paul Eggert
2016-05-11 7:23 ` Michael Albinus
2016-05-11 9:45 ` Stephen Berman
2016-05-11 15:08 ` Michael Albinus
2016-05-11 19:02 ` Stephen Berman
2016-05-11 19:11 ` Michael Albinus
2016-05-11 19:31 ` Stephen Berman
2016-05-11 19:32 ` Stephen Berman
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=572E9CCB.7070401@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=michael.albinus@gmx.de \
/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).