From: Michael Welsh Duggan <mwd@md5i.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mwd@md5i.com, acm@muc.de, 48446@debbugs.gnu.org, akrl@sdf.org
Subject: bug#48446: 28.0.50; Native compile failure during bootstrap
Date: Sun, 16 May 2021 01:22:32 -0400 [thread overview]
Message-ID: <87tun3tfqf.fsf@md5i.com> (raw)
In-Reply-To: <83fsynx435.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 May 2021 21:08:14 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 15 May 2021 20:17:00 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: Alan Mackenzie <acm@muc.de>, 48446@debbugs.gnu.org
>>
>> As you see, the native_comp_u member is non-NULL. But still Ffuncall
>> called funcall_subr, which AFAIU means it thought that
>> Qminibuffer_inactive_mode is not a natively-compiled function.
>>
>> What are we missing in this case? why doesn't Emacs recognize
>> Qminibuffer_inactive_mode as a natively-compiled function? Is this
>> too early during startup, and if so, how to we call Lisp at this
>> stage?
>
> I think I succeeded to fix this now, but I'd still like to know
> why the original code was wrong and how to avoid that in the future.
Your further questions are surely worth getting answered, but I can
attest that your patch solves this problem for me. Thank you!
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2021-05-16 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 16:40 bug#48446: 28.0.50; Native compile failure during bootstrap Michael Welsh Duggan
2021-05-15 17:17 ` Eli Zaretskii
2021-05-15 18:08 ` Eli Zaretskii
2021-05-15 18:21 ` Eli Zaretskii
2021-05-16 8:00 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-16 9:01 ` Eli Zaretskii
2021-05-16 5:22 ` Michael Welsh Duggan [this message]
2021-05-16 5: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=87tun3tfqf.fsf@md5i.com \
--to=mwd@md5i.com \
--cc=48446@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=akrl@sdf.org \
--cc=eliz@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).