From: Eli Zaretskii <eliz@gnu.org>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: 58267@debbugs.gnu.org
Subject: bug#58267: 29.0.50; Native-compiling the same files at every start
Date: Mon, 03 Oct 2022 19:51:46 +0300 [thread overview]
Message-ID: <83wn9gyhnh.fsf@gnu.org> (raw)
In-Reply-To: <CAOpc7mHxhS_LJ7Mcu7Mhf-_VfFmU2+0Q9mA=g6GXt=Yzh5e_iQ@mail.gmail.com> (message from Holger Schurig on Mon, 3 Oct 2022 00:11:38 -0700)
> From: Holger Schurig <holgerschurig@gmail.com>
> Date: Mon, 3 Oct 2022 00:11:38 -0700
>
> So, when I stop Emacs and start it again, I get the same behavior.
>
> I think the underlying problem is that /usr/local/share is root owned,
> and my running Emacs as a user don't have write access. So no *.eln
> files end up in this path. And this makes Emacs trying to byte-compile
> them again.
But Emacs is not supposed to write the *.eln files into
/usr/local/share, it's supposed to write them to your
.emacs.d/eln-cache directory under your home directory. Is your home
directory writable? What is the value of native-comp-eln-load-path in
that session?
> Couldn't Emacs byte-compile them at "make" or "make install" steps?
How would that help if Emacs is unable to write the *.eln files for
some reason?
next prev parent reply other threads:[~2022-10-03 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 7:11 bug#58267: 29.0.50; Native-compiling the same files at every start Holger Schurig
2022-10-03 16:51 ` Eli Zaretskii [this message]
2022-10-04 19:20 ` Holger Schurig
2022-10-04 19:45 ` Eli Zaretskii
[not found] ` <CAOpc7mE64zSG_R1v8u=myBuL=QLmURqERwqSJae-w096Ru5fKA@mail.gmail.com>
2022-10-05 5:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wn9gyhnh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58267@debbugs.gnu.org \
--cc=holgerschurig@gmail.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 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.