unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mauricio@collares.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: Tue, 16 Mar 2021 08:27:03 +0000	[thread overview]
Message-ID: <xjfmtv3y04o.fsf@sdf.org> (raw)
In-Reply-To: <83tupbeq3z.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Mar 2021 05:26:08 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: 47169@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
>> Date: Mon, 15 Mar 2021 20:14:55 +0000
>> 
>> 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?
>
> I agree.

Okay f3abb17118 should implement this.

Mauricio could you try if this works for you?

Thanks

  Andrea





  reply	other threads:[~2021-03-16  8:27 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
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 [this message]
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

  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=xjfmtv3y04o.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 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).