From: Eli Zaretskii <eliz@gnu.org>
To: Ioannis Kappas <ioannis.kappas@gmail.com>
Cc: 57880@debbugs.gnu.org, akrl@sdf.org
Subject: bug#57880: 28.1; Emacs crashes with native compilation on when some antivirus program is running on MS-Windows
Date: Thu, 22 Sep 2022 11:26:19 +0300 [thread overview]
Message-ID: <83tu4zstlg.fsf@gnu.org> (raw)
In-Reply-To: <CAMRHuGB-W9xWrV++Wf-VE8JweoUr2Xfgt2MY6hnDF83xk6hP3Q@mail.gmail.com> (message from Ioannis Kappas on Thu, 22 Sep 2022 07:55:03 +0100)
> From: Ioannis Kappas <ioannis.kappas@gmail.com>
> Date: Thu, 22 Sep 2022 07:55:03 +0100
> Cc: akrl@sdf.org, 57880@debbugs.gnu.org
>
> Or could there be an early init option to bypass the native compilation. This
> way the users can test the issue with is native comp.
There is one already.
> > Why does the directory where the *.eln files live matter? Doesn't the
> > antivirus software check any loading of any DLL from anywhere on the
> > system?
>
> Perhaps it only matters for the User directory. AVs want to put more
> stricter control
> on the binaries the user downloads and installs themselves.
Is that known, or is this just a guess?
Also, I asked which AV software has this problem. Do you happen to
know?
Anyway, programs are not normally installed under C:\Users, they are
installed under C:\Program Files.
> > In any case, the *.eln files have at least two places on any system,
> > and only one of them can be changed, the other one is fixed by the
> > build.
>
> Those precompiled with Emacs are fine in this use case since they are
> not stored in the Users directory, it's only newly compiled files that
> exhibit this issue because they store the .eln files in the user dir by
> default.
This means that the problem will only affect people who have libgccjit
and GCC/Binutils installed, because otherwise Emacs will be unable to
compile new *.eln files. Right?
next prev parent reply other threads:[~2022-09-22 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 11:14 bug#57880: 28.1; Emacs crashes with native compilation on when some antivirus program is running on MS-Windows Ioannis Kappas
2022-09-19 8:13 ` Andrea Corallo
2022-09-20 16:43 ` Ioannis Kappas
2022-09-21 11:06 ` Eli Zaretskii
2022-09-21 17:19 ` Ioannis Kappas
2022-09-22 6:36 ` Eli Zaretskii
2022-09-22 6:55 ` Ioannis Kappas
2022-09-22 8:26 ` Eli Zaretskii [this message]
2022-09-22 20:46 ` Ioannis Kappas
2022-09-23 5:53 ` Eli Zaretskii
2022-09-23 16:43 ` Ioannis Kappas
2023-06-07 21:13 ` Andrea Corallo
2023-06-08 5:31 ` Eli Zaretskii
2022-09-21 19:26 ` Andrea Corallo
2022-09-22 6:38 ` Eli Zaretskii
2022-09-22 8:09 ` 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=83tu4zstlg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57880@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=ioannis.kappas@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).