all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52138@debbugs.gnu.org, 51308@debbugs.gnu.org, akrl@sdf.org
Subject: bug#52138: bug#51308: bug#52138: 29.0.50; Some tests fail on emba when run with native compilation
Date: Sun, 13 Mar 2022 18:40:58 +0200	[thread overview]
Message-ID: <83r175ls9x.fsf@gnu.org> (raw)
In-Reply-To: <87fsnmuefz.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  13 Mar 2022 15:14:56 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 51308@debbugs.gnu.org,  52138@debbugs.gnu.org,  akrl@sdf.org
> Date: Sun, 13 Mar 2022 15:14:56 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > And what about loading a .el or .elc
> > file with an explicit extension -- that should NOT trigger
> > native-compilation even if there's no up-to-date .eln file.
> 
> Didn't try that.  Let's see...  if I do
> 
> (load "~/src/emacs/trunk/lisp/battery.el")
> 
> or
> 
> (load "~/src/emacs/trunk/lisp/battery.elc")
> 
> then no .eln compilation is started.

Great, that's the correct behavior.  Thanks.





  reply	other threads:[~2022-03-13 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 18:20 bug#51308: 29.0.50; A number of tests fail with AOT Lars Ingebrigtsen
2021-10-20 18:28 ` Eli Zaretskii
2021-10-21  3:04   ` Lars Ingebrigtsen
2021-10-21  4:20 ` Lars Ingebrigtsen
2022-03-12 21:32   ` bug#51308: bug#52138: 29.0.50; Some tests fail on emba when run with native compilation Lars Ingebrigtsen
2022-03-13  5:45     ` Eli Zaretskii
2022-03-13 14:14       ` Lars Ingebrigtsen
2022-03-13 16:40         ` Eli Zaretskii [this message]
2021-10-21  4:31 ` bug#51308: 29.0.50; A number of tests fail with AOT Lars Ingebrigtsen
2022-03-12 21:42   ` bug#51308: bug#52138: 29.0.50; Some tests fail on emba when run with native compilation Lars Ingebrigtsen

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=83r175ls9x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51308@debbugs.gnu.org \
    --cc=52138@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=larsi@gnus.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.