From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mauricio Collares <mauricio@collares.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 47169@debbugs.gnu.org
Subject: bug#47169: 28.0.50; [feature/native-comp] native-compiler-error-empty-byte when batch-native-compiling is confusing to users
Date: Mon, 15 Mar 2021 20:14:55 +0000 [thread overview]
Message-ID: <xjfzgz4xjgg.fsf@sdf.org> (raw)
In-Reply-To: <871rcgiamc.fsf@collares.org> (Mauricio Collares's message of "Mon, 15 Mar 2021 14:34:51 -0300")
Mauricio Collares <mauricio@collares.org> writes:
> Some packages contain valid .el files such that batch-byte-compiling
> them does not produce an .elc file, for example because they set
> "no-byte-compile" to t. Running batch-byte-compile on such a file exits
> successfully (without outputting any .elc file, of course) but running
> batch-native-compile exits with native-compiler-error-empty-byte.
>
> In the Nix package manager, we native-compile packages at installation
> time, and we do so by calling batch-native-compile for each .el file in
> the package separately. So in our use case .el files as described above
> shouldn't trigger error messages. We can work around this on the Nix
> side, but I was wondering if it would be better to turn the error into a
> warning (or even not emit a warning at all, since technically everything
> went well).
>
> Step to reproduce: batch-native-compile a file that sets no-byte-compile
> to t.
>
> (Reporting this on behalf of a user, see
> https://github.com/nix-community/emacs-overlay/issues/120)
>
> Best,
> Mauricio
Hi Mauricio, thanks for the report.
I think we have two option:
1- Assume that `no-byte-compile' implies also `no-native-compile' so
that we don't produce the .eln and we don't complain when
`no-byte-compile' is non-nil.
2- Manually add `no-native-compile' to all files we don't want to be
compiled.
I'll vote for 1, Eli WDYT?
Thanks
Andrea
next prev parent reply other threads:[~2021-03-15 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 17:34 bug#47169: 28.0.50; [feature/native-comp] native-compiler-error-empty-byte when batch-native-compiling is confusing to users Mauricio Collares
2021-03-15 20:14 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-16 3:26 ` Eli Zaretskii
2021-03-16 8:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 17:17 ` Mauricio Collares
2021-03-16 18:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 21:38 ` Mauricio Collares
2021-03-16 21:46 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfzgz4xjgg.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=47169@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=mauricio@collares.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.