[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (Windows) Problems with processes on master branch
From: |
Óscar Fuentes |
Subject: |
Re: (Windows) Problems with processes on master branch |
Date: |
Sun, 03 Mar 2024 00:17:13 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Arash Esbati <arash@gnu.org> writes:
> With my Emacs 30 (d0766c0999) build, started from cmd.exe with
> 'runemacs -Q' and M-x shell RET, I get:
>
> Microsoft Windows [Version 10.0.19045.4046]
> (c) Microsoft Corporation. Alle Rechte vorbehalten.
>
> z:dir\>gcc -v
> gcc -v
> Using built-in specs.
> ...
>
>
> With 'emacs -Q' started from a MinGW64 shell, M-x shell RET says:
>
> bash: cannot set terminal process group (-1): Inappropriate ioctl for device
> bash: no job control in this shell
>
> $ gcc -v
> Using built-in specs.
> ...
>
> Both versions work, despite the bash message. I didn't try eshell.
Thanks Arash and Corwin.
The problem is caused by MSYS2 makepkg-mingw (the MSYS2 binary package
builder) which adds
-D_FORTIFY_SOURCE
to CFLAGS. In fact, the MSYS2/Mingw-packages recipe for emacs-29
contains:
# -D_FORTIFY_SOURCE breaks build
CFLAGS=${CFLAGS//"-Wp,-D_FORTIFY_SOURCE=2"}
# -foptimize-sibling-calls breaks native compilation (GCC 13.1)
CFLAGS+=" -fno-optimize-sibling-calls"
Once that is added to my recipe, the problem goes away.