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: No Wayman <iarchivedmywholelife@gmail.com>, 64226@debbugs.gnu.org
Subject: bug#64226: 30.0.50; emacs-lisp-native-compile-and-load permission error
Date: Sun, 25 Jun 2023 11:02:41 -0400	[thread overview]
Message-ID: <yp1pm5j7ffy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83cz1n2xjp.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Jun 2023 20:53:46 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: No Wayman <iarchivedmywholelife@gmail.com>
>> Cc: acorallo@gnu.org, 64226@debbugs.gnu.org
>> Date: Thu, 22 Jun 2023 13:21:49 -0400
>> 
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>>  
>> > What is the value of native-comp-eln-load-path?
>> 
>> ("/home/n/.emacs.d/eln-cache/" 
>> "/usr/lib/emacs/30.0.50/native-lisp/")
>> 
>>  
>> > Also, can you show the contents of the file being compiled, 
>> > which
>> > seems to be /home/n/.emacs.d/elpaca/repos/elpaca/elpaca.el ?
>> 
>> I can reproduce with any elisp file.
>> e.g. $HOME/test.el containing:
>> 
>> --8<---------------cut here---------------start------------->8---
>> ;; -*- lexical-binding: t; -*-
>> (defun +test () (message "PASS"))
>> --8<---------------cut here---------------end--------------->8---
>
> Then I'm stumped, and hope Andrea will be able to figure this out.  I
> cannot reproduce the problem on my system, FWIW.

That's very bizzare to me as well, I can't reproduce this either.  Is
anyone able to reproduce this?

Thanks

  Andrea





  reply	other threads:[~2023-06-25 15:02 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 [this message]
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
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=yp1pm5j7ffy.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).