From: "T.V Raman" <raman@google.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Native Compile: Example Of Possibly Spurious Warning
Date: Mon, 17 May 2021 13:20:54 -0700 [thread overview]
Message-ID: <p91tun1jemx.fsf@google.com> (raw)
In-Reply-To: <xjfo8d9np2f.fsf@sdf.org> (Andrea Corallo's message of "Mon, 17 May 2021 19:22:00 +0000")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 2391 bytes --]
Andrea Corallo <akrl@sdf.org> writes:
Hi Andrea,
emacspeak is at https://github.com/tvraman/emacspeak
I've tried many things, including batch native compiling emacspeak ---
and to ensure that a running Emacs did not end up polluting the
eln-cache, I did this while running an emacs that did not have native
support compiled in.
If after then killing the non-native emacs and start the Emacs with
native support, I still see the warning I showed in my email.
Not sure whether you'll have the cycles to run emacspeak itself --
you'll minimally need to install the espeak and espeak-ng packages to
get speech synthesis on Linux for Emacspeak to use.
Here is my suspicion:
When emacspeak is ormally compiled via make, it loads it's own loaddefs
file etc --- and I suspect that when Emacs itself compiles any of the
emacspeak modules while running, it doesn't pull in the prerequisites.
Also: I was hoping that once batch-native-compile had done its thing for
all the emacspeak modules, then a newly started emacs would not need to
compile those files; however this is not true -- with no further changes
to the source-code of those files, Emacs appears to recompile those
files on the fly -- dont know why. I've not fully understood how the
cacheing strategy works, but I suspect it's over-aggressive.
One final thought: for complex packages like Emacspeak that have their
own custom build rules, it would be nice if emacs' async native compile
cycle could be given access to those rules.
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: "T.V Raman" <raman@google.com>
>>> Cc: emacs-devel@gnu.org
>>> Date: Mon, 17 May 2021 06:58:17 -0700
>>>
>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>
>>>
>>> All of the spurious warnings I'm seeing dont appear in batch compilation
>>> with batch-byte-compile.
>>> Here is the file on Github:
>>>
>>> https://github.com/tvraman/emacspeak/blob/master/lisp/emacspeak-preamble.el#L91
>>
>> I hope Andrea will look into this and tell what causes the error (my
>> guess is some other file this one loads or requires, but that's just a
>> guess).
>
> I'll be happy to have a look this week.
>
> Raman can you share a sequence precise instructions I can follow to
> reproduce what you see?
>
> Thanks
>
> Andrea
--
Thanks,
--Raman
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2021-05-17 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 20:51 Native Compile: Example Of Possibly Spurious Warning T.V Raman
2021-05-17 6:01 ` Eli Zaretskii
2021-05-17 13:58 ` T.V Raman
2021-05-17 14:16 ` Eli Zaretskii
2021-05-17 19:22 ` Andrea Corallo via Emacs development discussions.
2021-05-17 20:20 ` T.V Raman [this message]
2021-05-17 16:12 ` T.V Raman
2021-05-17 19:25 ` Andrea Corallo via Emacs development discussions.
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=p91tun1jemx.fsf@google.com \
--to=raman@google.com \
--cc=akrl@sdf.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).