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>,
	Andrea Corallo <acorallo@gnu.org>
Cc: 64226@debbugs.gnu.org
Subject: bug#64226: 30.0.50; emacs-lisp-native-compile-and-load permission error
Date: Thu, 22 Jun 2023 18:34:24 +0300	[thread overview]
Message-ID: <83pm5n33zz.fsf@gnu.org> (raw)
In-Reply-To: <87bkh734u7.fsf@gmail.com> (message from No Wayman on Wed, 21 Jun 2023 12:58:40 -0400)

> From: No Wayman <iarchivedmywholelife@gmail.com>
> Date: Wed, 21 Jun 2023 12:58:40 -0400
> 
> 
> To reproduce:
> 
> 1. Find an elisp file located in $DIR which user has permission to 
> write to.
> (in the following backtrace, the file being compiled was located 
> at $HOME/.emacs.d/elpaca/builds/elpaca/elpaca.el)
> 2. M-x emacs-lisp-native-compile-and-load 
> 3. Observer the following error: 
> 
> Error: permission-denied (\"Creating file with prefix\" 
> \"Permission denied\" 
> \"/usr/lib/emacs/30.0.50/native-lisp/30.0.50-58a66af6/elpaca-0646d6fc-1256ece5\")
>   mapbacktrace(#f(compiled-function (evald func args flags) 
>   #<bytecode 0x835cf36bbae8692>))
>   debug-early-backtrace()
>   debug-early(error (permission-denied \"Creating file with 
>   prefix\" \"Permission denied\" 
>   \"/usr/lib/emacs/30.0.50/native-lisp/30.0.50-58a66af6/elpaca-0646d6fc-1256ece5\"))
>   make-temp-file(\"/usr/lib/emacs/30.0.50/native-lisp/30.0.50-58a66af6/elpaca-0646d6fc-1256ece5\" 
>   nil \".eln.tmp\" nil)
>   comp--compile-ctxt-to-file(\"/usr/lib/emacs/30.0.50/native-lisp/30.0.50-58a66af6/elpaca-0646d6fc-1256ece5.eln\")
>   comp-compile-ctxt-to-file(\"/usr/lib/emacs/30.0.50/native-lisp/30.0.50-58a66af6/elpaca-0646d6fc-1256ece5.eln\")
>   comp-final1()
>   load-with-code-conversion(\"/tmp/emacs-int-comp-elpaca-0646d6fc-1256ece5-73Dpd0.el\" 
>   \"/tmp/emacs-int-comp-elpaca-0646d6fc-1256ece5-73Dpd0.el\" nil 
>   t)
>   command-line-1((\"-l\" 
>   \"/tmp/emacs-int-comp-elpaca-0646d6fc-1256ece5-73Dpd0.el\"))
>   command-line()
>   normal-top-level()
> 
> I would expect compiling this to not signal an error for a file I 
> have permission to write.

Is this in "emacs -Q"?  If not, please see if "emacs -Q" reproduces
the problem.

I also don't understand why the backtrace above seems to imply that
you invoked Emacs like this:

  emacs -l /tmp/emacs-int-comp-elpaca-0646d6fc-1256ece5-73Dpd0.el

IOW, the backtrace doesn't show invocation of
emacs-lisp-native-compile-and-load, it shows the attempt to load an
already-compiled .eln file.  What am I missing?  I added Andrea to
this discussion.

If, in "emacs -Q", you visit the source file, that is

  $HOME/.emacs.d/elpaca/builds/elpaca/elpaca.el

and then type

  M-: (native-compile buffer-file-name) RET

what file name do you see in the echo-area after the compilation
finishes?





  reply	other threads:[~2023-06-22 15:34 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 [this message]
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
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=83pm5n33zz.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).