From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: "make autoloads" signals an error
Date: Wed, 01 Jun 2022 14:26:31 +0200 [thread overview]
Message-ID: <87sfoozi14.fsf@gnus.org> (raw)
In-Reply-To: <83ee08h9et.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 01 Jun 2022 15:10:02 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Error: wrong-type-argument (integer-or-marker-p nil)
> mapbacktrace(#f(compiled-function (evald func args flags) #<bytecode -0x2d78d25b45e2f81>))
> debug-early-backtrace()
> debug-early(error (wrong-type-argument integer-or-marker-p nil))
> loaddefs-generate(("." "./c
I'm unable to reproduce this -- "make autoloads" just says
GEN loaddefs.el
INFO Scraping files for loaddefs...
INFO Scraping files for loaddefs...done
Does "make autoloads-force" also fail for you? In that case, perhaps
there's a bug in the code that's computing the updates, and in that
case, it depends on which files are newer than loaddefs.el. Hm...
Could you try removing the "c" from "elc" here:
$(lisp)/loaddefs.el: gen-lisp $(LOADDEFS)
$(AM_V_GEN)$(emacs) \
-l $(lisp)/emacs-lisp/loaddefs-gen.elc \
-f loaddefs-generate-batch $(lisp)/loaddefs.el ${SUBDIRS_ALMOST}
That should give us a more detailed backtrace.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-01 12:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 12:10 "make autoloads" signals an error Eli Zaretskii
2022-06-01 12:26 ` Lars Ingebrigtsen [this message]
2022-06-01 12:44 ` Eli Zaretskii
2022-06-01 12:46 ` Lars Ingebrigtsen
2022-06-01 12:50 ` Lars Ingebrigtsen
2022-06-01 12:56 ` Lars Ingebrigtsen
2022-06-01 17:51 ` Ergus
2022-06-01 18:21 ` Ergus
2022-06-02 9:16 ` Lars Ingebrigtsen
2022-06-02 10:01 ` Yuri D'Elia
2022-06-02 10:08 ` Lars Ingebrigtsen
2022-06-02 10:48 ` Lars Ingebrigtsen
2022-06-02 10:55 ` Eli Zaretskii
2022-06-02 11:20 ` Lars Ingebrigtsen
2022-06-02 11:53 ` Eli Zaretskii
2022-06-02 11:59 ` Lars Ingebrigtsen
2022-06-02 12:05 ` Eli Zaretskii
2022-06-03 3:13 ` Lars Ingebrigtsen
2022-06-03 5:57 ` Eli Zaretskii
2022-06-02 12:54 ` Andreas Schwab
2022-06-02 11:55 ` Lars Ingebrigtsen
2022-06-01 13:11 ` 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=87sfoozi14.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).