all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Cyril Arnould <cyril.arnould@outlook.com>
Cc: ofv@wanadoo.es, 73444@debbugs.gnu.org
Subject: bug#73444: 30.0.50; mingw-w64: Emacs uses CRT's `read` when _FORTIFY_SOURCE > 0
Date: Wed, 25 Sep 2024 14:46:47 +0300	[thread overview]
Message-ID: <86h6a4c5w8.fsf@gnu.org> (raw)
In-Reply-To: <PAWPR10MB776986E318800B89028B74F7F0682@PAWPR10MB7769.EURPRD10.PROD.OUTLOOK.COM> (message from Cyril Arnould on Wed, 25 Sep 2024 00:25:23 +0200)

merge 73444 63752
thanks

> Date: Wed, 25 Sep 2024 00:25:23 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>
> From: Cyril Arnould <cyril.arnould@outlook.com>
> 
>  > AFAIK the workaround on this bug report fixes #63752. CCing the original
>  > bug reporter, just in case.
> 
> I've tested the workaround applied to master and AFAICT it fixes #63752. 
> Emacs
> was pretty much unusable throughout in the bugged build, with the workaround
> it behaves normally.

Thanks, I'm therefore merging these two bugs.

P.S. Please in the future keep the bug address on the CC list.





  parent reply	other threads:[~2024-09-25 11:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PAWPR10MB776986E318800B89028B74F7F0682@PAWPR10MB7769.EURPRD10.PROD.OUTLOOK.COM>
2024-09-25 10:13 ` bug#73444: 30.0.50; mingw-w64: Emacs uses CRT's `read` when _FORTIFY_SOURCE > 0 Óscar Fuentes
2024-09-25 11:46 ` Eli Zaretskii [this message]
2024-09-23 22:15 Óscar Fuentes
     [not found] ` <handler.73444.B.17271297536353.ack@debbugs.gnu.org>
2024-09-23 22:29   ` Óscar Fuentes
2024-09-24 11:51     ` Eli Zaretskii
2024-09-24 12:34       ` Óscar Fuentes
2024-09-24 13:12         ` Eli Zaretskii
2024-09-24 14:06           ` Óscar Fuentes
2024-09-24 15:36             ` Eli Zaretskii
2024-09-24 11:48 ` Eli Zaretskii
2024-09-24 12:55   ` Óscar Fuentes
2024-09-24 13:27     ` Eli Zaretskii
2024-09-30 16:10       ` Óscar Fuentes

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86h6a4c5w8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73444@debbugs.gnu.org \
    --cc=cyril.arnould@outlook.com \
    --cc=ofv@wanadoo.es \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.