unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 70889@debbugs.gnu.org, cyril.arnould@outlook.com
Subject: bug#70889: 29.3; GCC14.1 MinGW compilation error
Date: Mon, 13 May 2024 07:43:39 +0300	[thread overview]
Message-ID: <8634qmz5hg.fsf@gnu.org> (raw)
In-Reply-To: <3b4c258f-1685-450a-b041-ddcc866143e2@cs.ucla.edu> (message from Paul Eggert on Sun, 12 May 2024 12:18:53 -0700)

> Date: Sun, 12 May 2024 12:18:53 -0700
> Cc: 70889@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 
> On 2024-05-12 10:16, Eli Zaretskii wrote:
> 
> >> Oh, I hadn't seen that. Yep, with this flag the configure script's
> >> errors turn into warnings and subsequent the compilation error is
> >> gone.
> > 
> > Then I guess we should use that on MS-Windows when running the
> > configure script.  Paul, is there a better way.
> 
> In the short run, having 'configure' use 
> -Wno-error=implicit-function-declaration on MS-Windows should work 
> around the issue. Eventually, though, I suspect it'll cause further 
> problems, as the C standard indeed prohibits implicit function declarations.

I didn't mean to use this when building Emacs, only when running the
test programs of the configure script.





  reply	other threads:[~2024-05-13  4:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12  7:29 bug#70889: 29.3; GCC14.1 MinGW compilation error Cyril Arnould
2024-05-12  8:24 ` bug#70890: " Cyril Arnould
2024-05-12 10:22   ` Eli Zaretskii
2024-05-12 10:31 ` bug#70889: " Eli Zaretskii
2024-05-12 12:52   ` Cyril Arnould
2024-05-12 14:49     ` Eli Zaretskii
2024-05-12 15:04       ` Cyril Arnould
2024-05-12 15:39         ` Eli Zaretskii
2024-05-12 16:21           ` Cyril Arnould
2024-05-12 17:16             ` Eli Zaretskii
2024-05-12 19:18               ` Paul Eggert
2024-05-13  4:43                 ` Eli Zaretskii [this message]
2024-05-17 17:19                   ` Cyril Arnould
2024-05-17 17:41                     ` Eli Zaretskii
2024-05-19  8:01                   ` Eli Zaretskii
2024-05-19 10:06                     ` Cyril Arnould
2024-05-19 10:24                       ` Eli Zaretskii

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=8634qmz5hg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70889@debbugs.gnu.org \
    --cc=cyril.arnould@outlook.com \
    --cc=eggert@cs.ucla.edu \
    /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).