From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 37445@debbugs.gnu.org, eggert@cs.ucla.edu, tino.calancha@gmail.com
Subject: bug#37445: 27.0.50; Permission denied after make install
Date: Fri, 20 Sep 2019 10:00:37 +0300 [thread overview]
Message-ID: <83blvftpt6.fsf@gnu.org> (raw)
In-Reply-To: <alpine.LNX.2.21.99999.362.1909200557580.3673@ip-10-207-252-54.us-west-2.compute.internal> (message from Tino Calancha on Fri, 20 Sep 2019 06:07:54 +0000 (UTC))
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Fri, 20 Sep 2019 06:07:54 +0000 (UTC)
> Cc: 37445@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
>
> # Add (require 'ert) at the botton: this seems to fire the issue
> $ echo "(require 'ert)" >> .emacs
>
> # Now launch Emacs: you will see at *Warnings* buffer
> # File error: Testing file, Permission denied, /home/ec2-user/soft/emacs-master/src
>
> # Now, if you want you can try:
> M-: (require 'ert) RET
> Testing file: Permission denied, /home/ec2-user/soft/emacs-master/src
Can you show the C and Lisp backtraces for that error? You can run
Emacs under GDB with a breakpoint on this line of fileio.c:
static Lisp_Object
file_metadata_errno (char const *action, Lisp_Object file, int err)
{
if (err == ENOENT || err == ENOTDIR || err == 0)
return Qnil;
report_file_errno (action, file, err); <<<<<<<<<<<<<<<<<<<<<<<<<<
}
Thanks.
next prev parent reply other threads:[~2019-09-20 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 9:02 bug#37445: 27.0.50; Permission denied after make install Tino Calancha
2019-09-18 19:12 ` Paul Eggert
2019-09-19 6:57 ` Paul Eggert
2019-09-19 11:35 ` Tino Calancha
2019-09-19 17:41 ` Paul Eggert
2019-09-20 6:07 ` Tino Calancha
2019-09-20 7:00 ` Eli Zaretskii [this message]
2019-09-20 9:10 ` Paul Eggert
2019-09-20 12:40 ` Eli Zaretskii
2019-09-20 18:17 ` Paul Eggert
2019-09-20 18:59 ` Eli Zaretskii
2019-09-20 19:33 ` Paul Eggert
2019-09-21 6:07 ` Eli Zaretskii
2019-09-26 20:11 ` Paul Eggert
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=83blvftpt6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37445@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=tino.calancha@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.