unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Colin McLear <mclear@fastmail.com>
Cc: 53891@debbugs.gnu.org
Subject: bug#53891: 29.0.50; native comp eln cache
Date: Wed, 09 Feb 2022 15:54:24 +0200	[thread overview]
Message-ID: <83tud8uovj.fsf@gnu.org> (raw)
In-Reply-To: <50BDF7A0-8309-4B39-A26B-75BBB72017F5@fastmail.com> (message from Colin McLear on Tue, 08 Feb 2022 23:10:24 -0500)

> From: Colin McLear <mclear@fastmail.com>
> Date: Tue, 08 Feb 2022 23:10:24 -0500
> 
> On recent version from emacs-master I've noticed that I can no longer
> reliably set the eln-cache. I have the following in my early-init.el:
> 
> ```
> ;; Dir for eln-cache
> (when (boundp 'native-comp-eln-load-path)
> (setcar native-comp-eln-load-path
> (expand-file-name (convert-standard-filename ".local/temp/cache/eln-cache/")
> user-emacs-directory)))
> 
> ;; Silence nativecomp warnings popping up
> (setq native-comp-async-report-warnings-errors nil)
> 
> ;; Settings
> (setq native-comp-speed 2
> native-comp-deferred-compilation t
> package-native-compile t)
> ```
> But this isn't reliably setting the cache and I've had to rever to an
> earlier commit where things worked (as reported in the versio info).

This was never supported.  That it used to work for you was just luck.

Since it sounds like people want to divert the eln-cache directory to
custom places, something we didn't envision, we should support it
correctly: by making the "eln-cache" directory name customizable
instead of hard-coded.

I will work on adding such a feature.  Please stay tuned.





  parent reply	other threads:[~2022-02-09 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  4:10 bug#53891: 29.0.50; native comp eln cache Colin McLear
2022-02-09  8:07 ` Lars Ingebrigtsen
2022-02-09 13:54 ` Eli Zaretskii [this message]
2022-02-10  4:46   ` Colin McLear
2022-02-10  8:38   ` Eli Zaretskii
2022-02-10 15:24     ` Colin McLear
2022-02-10 17:31       ` Eli Zaretskii

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=83tud8uovj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53891@debbugs.gnu.org \
    --cc=mclear@fastmail.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).