From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Problem with native-compilation
Date: Fri, 25 Mar 2022 10:04:16 +0300 [thread overview]
Message-ID: <834k3mcy33.fsf@gnu.org> (raw)
In-Reply-To: <87bkxvyozh.fsf@jonas-damm.de> (message from Jonas Damm on Thu, 24 Mar 2022 23:17:38 +0100)
> From: Jonas Damm <emails@jonas-damm.de>
> Date: Thu, 24 Mar 2022 23:17:38 +0100
>
> I compiled Emacs with the native-compilation option.
Which version of Emacs?
> After installing
> the org-contacts package from nongnu org-contrib, at first everything
> works as expected.
>
> However, after the compiling in the background is done, some functions
> are broken:
>
>
> Warning (comp): org-contacts.el:648:13: Warning: the function ‘start’ is not known to be defined. Disable showing Disable logging
> Warning (comp): org-contacts.el:593:12: Warning: the function ‘lexical-let*’ is not known to be defined. Disable showing Disable logging
> Warning (comp): org-contacts.el:505:4: Warning: the function ‘list*’ is not known to be defined. Disable showing Disable logging
> Warning (comp): org-contacts.el:459:4: Warning: the function ‘lexical-let’ is not known to be defined. Disable showing Disable logging
> Warning (comp): org-contacts.el:372:28: Warning: the function ‘values’ is not known to be defined. Disable showing Disable logging
> Warning (comp): org-contacts.el:330:44: Warning: the function ‘first’ is not known to be defined. Disable showing Disable logging
>
>
>
> After this, message-tab does not work anymore so i can not complete
> addresses in mu4e anymore.
What is org-contacts.el? I don't see it in Emacs.
From the messages you show, it sounds like org-contacts.el has
problems that are flagged by the native compilation, in particular it
needs to (require 'cl) (for lexical-let*) and probably other packages
to resolve the other "not known to be defined" problems.
You need to be aware that JIT native compilation happens in a separate
pristine Emacs process, which doesn't know about any packages you have
loaded in the process that requests the compilation. So native
compilation flags any problems caused by compiling a file in "emacs -Q".
next prev parent reply other threads:[~2022-03-25 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 22:17 Problem with native-compilation Jonas Damm
2022-03-25 7:04 ` Eli Zaretskii [this message]
2022-03-26 13:58 ` Felix Dietrich
2022-03-26 14:38 ` Eli Zaretskii
2022-04-04 10:50 ` Felix Dietrich
2022-04-03 17:57 ` Jonas Damm
2022-04-04 13:01 ` Felix Dietrich
[not found] <87wngio1qo.fsf@jonas-damm.de>
2022-03-25 10:17 ` Eli Zaretskii
2022-03-25 10:36 ` Jonas Damm
2022-03-25 11:24 ` Eli Zaretskii
2022-03-25 18:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=834k3mcy33.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).