> From: Bruno Haible <[email protected]> > Cc: Paul Eggert <[email protected]>, [email protected], [email protected] > Date: Thu, 06 Nov 2025 00:18:58 +0100 > > > building Emacs does not compile > > stdio-consolesafe.c, and I cannot see why. Can you or Bruno explain > > why this happens? > > ... > > In any case, I think we do want to compile and use > > stdio-consolesafe.c, for the benefit of programs in lib-src/, but we > > need to find a way of doing that without pulling in the above 3 > > modules. > > That's because stdio-consolesafe.c is part of the 'stdio-h' module, > which you have disabled.
Ah, okay. Now it all makes sense. > If you want stdio-consolesafe.c to be compiled although you don't import > the 'stdio-h' module, you can do so by creating a module 'stdio-h-emacs' > that includes just the appropriate definitions for this one source file. > See https://www.gnu.org/software/gnulib/manual/html_node/Extending-Gnulib.html > for this approach. I guess it's up to Paul, then: if he can afford creating such a module and import it, I can work on integrating it with Emacs and its auxiliary programs. Failing that, I guess we will steal the code from stdio-consolesafe.c into the Emacs sources to do the same without compiling the Gnulib file itself. > > There was one problem in this Gnulib merge which broke the MinGW build > > of Emacs, and that's the change in acl_entries.c. Evidently, no one > > envisioned that this file will be compiled in MinGW builds, but in > > Emacs it is compiled > > Thanks for the report. Should be fixed by the patch below. Thanks. As I wrote earlier, I've arranged not to compile acl_entries.c in the MinGW build, but it's good to know acl_entries.c will again compile to a no-op on MS-Windows.
