From: Eli Zaretskii <eliz@gnu.org>
To: "T.V Raman" <raman@google.com>, Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Native Compile: Example Of Possibly Spurious Warning
Date: Mon, 17 May 2021 17:16:10 +0300 [thread overview]
Message-ID: <83cztptphx.fsf@gnu.org> (raw)
In-Reply-To: <p91v97hxy12.fsf@google.com> (raman@google.com)
> 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).
> Separately: when I batch-byte-compile emacspeak, I pass in commandline
> flags that loads emacspeak-loaddefs.el (analogous to Emacs' own
> loaddefs.el)
> is it possible to batch-native-compile (that function does exist) but I
> have no idea where the generated files end up ie if they go somewhere
> different than when generated from a running Emacs.
They should all go to ~/.emacs.d/eln-cache/.
next prev parent reply other threads:[~2021-05-17 14:16 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 [this message]
2021-05-17 19:22 ` Andrea Corallo via Emacs development discussions.
2021-05-17 20:20 ` T.V Raman
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=83cztptphx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
/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).