unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: iarchivedmywholelife@gmail.com, 64226@debbugs.gnu.org
Subject: bug#64226: 30.0.50; emacs-lisp-native-compile-and-load permission error
Date: Sat, 12 Aug 2023 12:56:38 -0400	[thread overview]
Message-ID: <yp1jzu0ci7t.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <yp1sf8op8s6.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Sat, 12 Aug 2023 11:42:01 -0400")

Andrea Corallo <acorallo@gnu.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Andrea Corallo <acorallo@gnu.org>
>>> Cc: No Wayman <iarchivedmywholelife@gmail.com>,  64226@debbugs.gnu.org
>>> Date: Wed, 09 Aug 2023 09:22:35 -0400
>>> 
>>> Okay I pushed b93107c20b2 to fix this.  I tested as best as I could but
>>> tweaking these dynamic variables is always tricky.
>>
>> These changes broke building Emacs in the source tree: now all the
>> *.eln files produced by the build's ELC+ELN rule are written to the
>> user's eln-cache directory instead of into native-lisp subdirectory of
>> the build tree.  To reproduce, touch, say, lisp/files.el or delete
>> lisp/files.elc, and then say "make" -- you will see that the *.eln
>> file is written under ~/.emacs.d/eln-cache, and if you also delete the
>> corresponding files-NNNN.eln file from native-lisp, Emacs will load
>> files.elc during loadup.
>
> Thanks, looking at it.

Okay, just pushed 842dbf500e0, seems to solve the issue here for me,
please have a look.

Thanks!

  Andrea





  reply	other threads:[~2023-08-12 16:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 16:58 bug#64226: 30.0.50; emacs-lisp-native-compile-and-load permission error No Wayman
2023-06-22 15:34 ` Eli Zaretskii
2023-06-22 15:44   ` No Wayman
2023-06-22 16:12     ` Eli Zaretskii
2023-06-22 16:22       ` No Wayman
2023-06-22 17:16         ` Eli Zaretskii
2023-06-22 17:21           ` No Wayman
2023-06-22 17:53             ` Eli Zaretskii
2023-06-25 15:02               ` Andrea Corallo
2023-07-01  8:36                 ` Eli Zaretskii
2023-07-01 15:28                   ` No Wayman
2023-07-01 15:41                     ` Eli Zaretskii
2023-07-01 19:14                       ` No Wayman
2023-07-02  5:59                         ` Eli Zaretskii
2023-07-02  6:08                           ` No Wayman
2023-07-03  8:50                           ` Andrea Corallo
2023-08-09 13:22                             ` Andrea Corallo
2023-08-09 15:24                               ` No Wayman
2023-08-09 16:29                                 ` Eli Zaretskii
2023-08-12  9:19                               ` Eli Zaretskii
2023-08-12 15:42                                 ` Andrea Corallo
2023-08-12 16:56                                   ` Andrea Corallo [this message]
2023-08-12 17:22                                     ` Eli Zaretskii
2023-06-25 14:44       ` Andrea Corallo

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=yp1jzu0ci7t.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=64226@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=iarchivedmywholelife@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 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).