Subject: bug#70889: 29.3; GCC14.1 MinGW compilation error

From: Eli Zaretskii <[email-masked]>
Date: Sun, 12 May 2024 18:39:54 +0300

> Date: Sun, 12 May 2024 17:04:30 +0200
> Cc: [email-masked]
> From: Cyril Arnould <[email-masked]>
> 
>  > So I'd like first to understand why a warning causes a compilation
>  > error.
> 
> This is a new feature of GCC 14, unless I'm misunderstanding
> something:
> 
> https://gcc.gnu.org/gcc-14/porting_to.html#warnings-as-errors

Which also says that turning these back into warnings is as simple as
adding -Wno-error=implicit-function-declaration.  Can you try that
(via CFLAGS=... setting when you run the configure script)?

>  > If we need to add to our w32 headers every single function that can
>  > fail the compilation of some test program, we will never recover
>  > from this slippery slope.
> 
> Would using the gnulib work instead of using emacs-proprietary w32
> headers? Mostly asking out of curiosity.

No.  Where we can use Gnulib we already do.