From: Dmitry Gutov <dmitry@gutov.dev>
To: 61917@debbugs.gnu.org, akrl@sdf.org
Subject: bug#61917: 29.0.60; native compilation issues
Date: Sun, 9 Apr 2023 20:48:05 +0300 [thread overview]
Message-ID: <108ec148-db08-1ff3-148f-a76ff657deae@gutov.dev> (raw)
In-Reply-To: <xjfbkkae55i.fsf@ma.sdf.org>
Hi Andrea and all,
On 30/03/2023 16:32, Andrea Corallo wrote:
>> I've confirmed that my build of emacs-29 ab4273056e0 works well.
>> Thank you very much for your great work.
>>
>> - Recompiled all .elc and .eln successfully.
>>
>> - .eln issues of both yasnippet and ddskk (Japanese input method) have gone.
>> They are successfully loaded, and work without any problem.
> Wonderful, thank you very much for reporting!
>
> Closing this then.
There was a report against company-mode which I just localized to this
bug: https://github.com/company-mode/company-mode/issues/1381
The symptoms looked different, though: more like one sees when a macro
definition is not loaded during byte-compilation ("Invalid function: xxx").
Just mentioning this here for posterity and better searchability.
next prev parent reply other threads:[~2023-04-09 17:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 15:18 bug#61917: 29.0.60; native compilation issues Al Haji-Ali
2023-03-02 15:48 ` Eli Zaretskii
[not found] ` <xjfzg8uxi7b.fsf@ma.sdf.org>
2023-03-09 10:08 ` Eli Zaretskii
2023-03-09 11:33 ` Andrea Corallo
2023-03-09 12:20 ` Eli Zaretskii
2023-03-09 16:35 ` Al Haji-Ali
2023-03-10 16:55 ` Andrea Corallo
[not found] ` <xjf4jqfqoy0.fsf@ma.sdf.org>
2023-03-23 15:43 ` Al Haji-Ali
2023-03-25 12:49 ` Naofumi Yasufuku
2023-03-25 14:46 ` Andrea Corallo
2023-03-25 19:55 ` Naofumi Yasufuku
2023-03-26 8:22 ` Andrea Corallo
2023-03-26 9:20 ` Andrea Corallo
2023-03-29 20:29 ` Andrea Corallo
2023-03-29 22:53 ` Naofumi Yasufuku
2023-03-30 13:14 ` Naofumi Yasufuku
2023-03-30 13:32 ` Andrea Corallo
2023-04-09 17:48 ` Dmitry Gutov [this message]
2023-03-10 16:54 ` Andrea Corallo
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=108ec148-db08-1ff3-148f-a76ff657deae@gutov.dev \
--to=dmitry@gutov.dev \
--cc=61917@debbugs.gnu.org \
--cc=akrl@sdf.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).