unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt M <mmerino@outlook.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "46972@debbugs.gnu.org" <46972@debbugs.gnu.org>
Subject: bug#46972: RE : bug#46972: 28.0.50; [feature/native-comp] Emacs locks itself during native compilation because of permission denied
Date: Sun, 14 Mar 2021 14:07:13 +0000	[thread overview]
Message-ID: <DB6P190MB0327D7449B08FB4A2DAD9FE4D66D9@DB6P190MB0327.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <83y2epg8i2.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

I just tested it and the problem doesn’t happen anymore. Thanks a lot !

De : Eli Zaretskii<mailto:eliz@gnu.org>
Envoyé le :dimanche 14 mars 2021 14:38
À : mmerino@outlook.fr<mailto:mmerino@outlook.fr>
Cc : 46972@debbugs.gnu.org<mailto:46972@debbugs.gnu.org>
Objet :Re: bug#46972: 28.0.50; [feature/native-comp] Emacs locks itself during native compilation because of permission denied

> Date: Sun, 14 Mar 2021 12:51:06 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 46972@debbugs.gnu.org
>
> Andrea, it looks like the inner loop in eln_load_path_final_clean_up
> isn't protected against errors?  IOW, if Fdelete_file signals an
> error, it won't be caught, is that right?

I've just had a similar situation myself, so I fixed the problem, I
hope.  Please try the latest native-comp branch and see if your
problem is solved.


[-- Attachment #2: Type: text/html, Size: 2489 bytes --]

  reply	other threads:[~2021-03-14 14:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 17:23 bug#46972: 28.0.50; [feature/native-comp] Emacs locks itself during native compilation because of permission denied Matt M
2021-03-06 18:34 ` Eli Zaretskii
2021-03-06 18:52   ` bug#46972: RE : " Matt M
2021-03-06 19:01     ` Eli Zaretskii
2021-03-06 19:02       ` bug#46972: RE : " Matt M
2021-03-06 20:03         ` Eli Zaretskii
2021-03-06 20:14           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-06 20:16             ` Eli Zaretskii
2021-03-12  0:26               ` bug#46972: RE : " Matt M
2021-03-12  7:36                 ` Eli Zaretskii
2021-03-12 11:37                   ` bug#46972: RE : " Matt M
2021-03-12 12:45                     ` Eli Zaretskii
2021-03-12 12:53                       ` bug#46972: RE : " Matt M
2021-03-14 10:51 ` Eli Zaretskii
2021-03-14 13:39   ` Eli Zaretskii
2021-03-14 14:07     ` Matt M [this message]
2021-03-14 14:24       ` bug#46972: RE : " Eli Zaretskii

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=DB6P190MB0327D7449B08FB4A2DAD9FE4D66D9@DB6P190MB0327.EURP190.PROD.OUTLOOK.COM \
    --to=mmerino@outlook.fr \
    --cc=46972@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).