From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrew Whatson <whatson@gmail.com>
Cc: 44209@debbugs.gnu.org, Andrea Corallo <akrl@sdf.org>
Subject: bug#44209: 28.0.50; [feature/native-comp] Compilation failure in progmodes/js.el
Date: Sun, 25 Oct 2020 16:02:18 +0100 [thread overview]
Message-ID: <87v9ey8i2t.fsf@gnus.org> (raw)
In-Reply-To: <CAPE069dwqSb5JpG2Yo3Dz+d6bXUQ_2a2AEXi41L-iBzriRJpkg@mail.gmail.com> (Andrew Whatson's message of "Mon, 26 Oct 2020 00:42:16 +1000")
Andrew Whatson <whatson@gmail.com> writes:
> I maintain both of these packages. Are you sure you're testing with
> "make NATIVE_FULL_AOT=1"? The error does not occur with the minimal
> bootstrap build, because that doesn't attempt to native-compile js.el
> during the build. I guess this error must occur at runtime with
> deferred compilation for non-AOT builds.
Oh, sorry, I assumed that
ELC+ELN progmodes/js.elc
meant that it was doing full ahead-of-time .eln generation... but it's
not? Andrea, perhaps the compilation output here should be tweaked,
then?
Anyway, with
$ make -j16 NATIVE_FULL_AOT=1 bootstrap
I do get the same error you're seeing:
ELC+ELN progmodes/js.elc
Symbol's function definition is void: cc-bytecomp-is-compiling
make[3]: *** [Makefile:314: progmodes/js.elc] Error 255
make[3]: Leaving directory '/home/larsi/src/emacs/native-compile/lisp'
make[2]: *** [Makefile:348: compile-main] Error 2
make[2]: Leaving directory '/home/larsi/src/emacs/native-compile/lisp'
make[1]: *** [Makefile:420: lisp] Error 2
make[1]: Leaving directory '/home/larsi/src/emacs/native-compile'
make: *** [Makefile:1143: bootstrap] Error 2
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-25 15:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 11:06 bug#44209: 28.0.50; [feature/native-comp] Compilation failure in progmodes/js.el Andrew Whatson
2020-10-25 13:16 ` Lars Ingebrigtsen
2020-10-25 13:52 ` Andrew Whatson
2020-10-25 14:25 ` Lars Ingebrigtsen
2020-10-25 14:42 ` Andrew Whatson
2020-10-25 14:55 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-25 15:11 ` Andrew Whatson
2020-10-25 15:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-25 15:02 ` Lars Ingebrigtsen [this message]
2020-10-25 15:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-25 15:57 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-25 16:13 ` Lars Ingebrigtsen
2020-10-25 21:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-25 23:06 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-25 23:44 ` Lars Ingebrigtsen
2020-10-26 1:08 ` Andrew Whatson
2020-10-26 7:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87v9ey8i2t.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44209@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=whatson@gmail.com \
/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).