From: "András Svraka" <svraka.andras@gmail.com>
To: "63752@debbugs.gnu.org" <63752@debbugs.gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Cyril Arnould <cyril.arnould@outlook.com>
Subject: bug#63752: 28.2; GCC 13.1 breaks Emacs subprocess handling when built with -D_FORTIFY_SOURCE
Date: Thu, 1 Jun 2023 09:31:10 +0200 [thread overview]
Message-ID: <733589BE-966F-4E82-8F9A-A36637741238@gmail.com> (raw)
In-Reply-To: <AS4PR10MB6110522B200DF954C6CC481EE3449@AS4PR10MB6110.EURPRD10.PROD.OUTLOOK.COM>
Dear all,
> On 2023. May 27., at 16:32, Cyril Arnould <cyril.arnould@outlook.com> wrote:
> > Which version of GCC is this, btw? If it's the latest GCC 13, did you
> > try downgrading to GCC 12?
> It's GCC 13.1, yes, I haven't tested GCC 12. I don't know how
> easy it is to downgrade GCC on MSYS2 though, I assume there's a
> lot of dependencies that can go wrong.
I tried downgrading to GCC 12.2 in MSY2 and the problem exist there as well.
> > FWIW, Emacs 28 and 29 (and also Emacs 30) builds fine for me with
> > MinGW, both with and without native-compilation, but I don't use
> > _FORTIFY_SOURCE (and don't plan on using it any time soon).
> This makes me wonder if GCC 13.1 Emacs builds with
> _FORTIFY_SOURCE are working fine in other operating systems? It's
> not something I can easily test, however.
Arch Linux also uses _FORTIFY_SOURCE and AFAIU MSYS2’s motivation was to follow them [1]. I did not test it though but couldn’t find related bug reports.
[1]: https://github.com/msys2/MSYS2-packages/pull/3222
next prev parent reply other threads:[~2023-06-01 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 12:57 bug#63752: 28.2; GCC 13.1 breaks Emacs subprocess handling when built with -D_FORTIFY_SOURCE Cyril Arnould
2023-05-27 13:42 ` Eli Zaretskii
2023-05-27 14:32 ` bug#63752: AW: " Cyril Arnould
2023-06-01 7:31 ` András Svraka [this message]
2023-06-30 22:41 ` Cyril Arnould
2023-07-01 6:40 ` Eli Zaretskii
2023-07-05 20:23 ` Cyril Arnould
2023-07-06 5:28 ` Eli Zaretskii
2023-07-06 19:28 ` Cyril Arnould
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=733589BE-966F-4E82-8F9A-A36637741238@gmail.com \
--to=svraka.andras@gmail.com \
--cc=63752@debbugs.gnu.org \
--cc=cyril.arnould@outlook.com \
--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).