procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; * etc/PROBLEMS: Mention MinGW problems with -D_FORTIFY_SOURCE=2.

Browse source
This commit is contained in:
Eli Zaretskii 2023-07-01 10:01:59 +03:00
parent a5bd9fb8c4
commit cc660bd265
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
etc/PROBLEMS
View file

@ -2768,6 +2768,21 @@ With any of the above methods, you'd need to restart Emacs (and
preferably also your Windows system) after making the changes, to have preferably also your Windows system) after making the changes, to have
them take effect. them take effect.
*** MinGW64 Emacs built with -D_FORTIFY_SOURCE=2 misbehaves
Using this preprocessor option when building Emacs with MinGW64
produces an Emacs binary that behaves incorrectly. In particular,
running asynchronous shell command, e.g., with 'M-&', causes Emacs to
use 100% of CPU and start allocating a lot of memory. For the same
reason, asynchronous native-compilation will hang Emacs (which could
wedge Emacs during startup, if your Emacs is configured to download
and install packages via package.el every startup). 'M-x run-python',
'M-x shell', and similar commands also hang. Other commands might
also cause high CPU and/or memory usage.
The workaround is to rebuild Emacs without the -D_FORTIFY_SOURCE=2
option.
** Emacs on Windows 9X requires UNICOWS.DLL ** Emacs on Windows 9X requires UNICOWS.DLL
If that DLL is not available, Emacs will display an error dialog If that DLL is not available, Emacs will display an error dialog