unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: No Wayman <iarchivedmywholelife@gmail.com>
Cc: acorallo@gnu.org, 64226@debbugs.gnu.org
Subject: bug#64226: 30.0.50; emacs-lisp-native-compile-and-load permission error
Date: Sun, 02 Jul 2023 08:59:32 +0300	[thread overview]
Message-ID: <834jmmq2ez.fsf@gnu.org> (raw)
In-Reply-To: <87bkgvwe05.fsf@gmail.com> (message from No Wayman on Sat, 01 Jul 2023 15:14:16 -0400)

> From: No Wayman <iarchivedmywholelife@gmail.com>
> Cc: acorallo@gnu.org, 64226@debbugs.gnu.org
> Date: Sat, 01 Jul 2023 15:14:16 -0400
> 
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > perhaps you could describe how to reproduce starting from "emacs
> > -Q" (and loading any packages or features you need for the minimal
> > reproduction recipe).  The way you were showing the problem until
> > now obviously depends on your local setup, which is impossible to
> > reproduce without knowing the details.
> 
> The instructions I gave here:
> 
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-06/msg01224.html
> 
> reproduce the error on my end from emacs -Q with a minimal file.
> To be crystal clear:
> 
> 1. Save the following file to $HOME/test.el (or any path where the 
> user has write permissions):
> 
> --8<---------------cut here---------------start------------->8---
> ;; -*- lexical-binding: t; -*-
> (defun +test () (message "PASS"))
> --8<---------------cut here---------------end--------------->8---
> 
> 2. emacs -Q $HOME/test.el
> 3. M-x emacs-lisp-native-compile-compile-and-load
> 4. Error is printed to message buffer.

Thanks.  I think Andrea couldn't reproduce this, but maybe he could
try again.  (The error will only happen if the directory
usr/lib/emacs/30.0.50/native-lisp is not writable by your user, so
ensuring it's not writable should be part of the recipe.)

Also, please show the backtrace corresponding to the above recipe.
The backtrace you posted mentions files like
/home/n/.emacs.d/elpaca/repos/elpaca/elpaca.el, but there's no
reference to $HOME/elpaca/repos in your recipe above.  So I presume
the backtrace with the above recipe will mention different files, and
it is important to see those file names.





  reply	other threads:[~2023-07-02  5:59 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 [this message]
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=834jmmq2ez.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64226@debbugs.gnu.org \
    --cc=acorallo@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).