unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org, andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs build fails on Windows mingw64
Date: Sun, 24 Oct 2021 16:58:36 +0300	[thread overview]
Message-ID: <8335oq4j8z.fsf@gnu.org> (raw)
In-Reply-To: <867fb020-c32b-3a42-1910-385756846c6d@cs.ucla.edu> (message from Paul Eggert on Sun, 24 Oct 2021 08:25:29 -0400)

> Cc: andrewjmoreton@gmail.com, bug-gnulib@gnu.org, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 24 Oct 2021 08:25:29 -0400
> 
> > ntlib cannot include config.h,
> > due to various redefinitions and redirections we do in ms-w32.h for
> > Emacs.
> 
> I now see Emacs has a symbol DEFER_MS_W3_H to deal with this glitch. So 
> how about the attached patch instead? If it doesn't suffice, presumably 
> something like DEFER_MS_W3_H would suffice.

We could try all that, but not on the release branch.  There, I'd like
a simple and safe fix.  Is such a thing possible?

Can you explain why config.h is needed there, and why only for GCC 11?

Thanks.



  reply	other threads:[~2021-10-24 13:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86v91nfp6e.fsf@gmail.com>
2021-10-24  3:45 ` Emacs build fails on Windows mingw64 Paul Eggert
2021-10-24  6:26   ` Eli Zaretskii
2021-10-24 10:50     ` Andy Moreton
2021-10-24 12:27       ` Paul Eggert
2021-10-24 12:25     ` Paul Eggert
2021-10-24 13:58       ` Eli Zaretskii [this message]
2021-10-24 17:05         ` Paul Eggert
2021-10-24 17:48           ` Eli Zaretskii
2021-10-24 17:57           ` Andy Moreton
2021-10-24 22:52             ` Bruno Haible
2021-10-25 11:52               ` Eli Zaretskii
2021-10-25 21:26               ` Andy Moreton
2021-10-24 18:01           ` Óscar Fuentes
2021-10-24 18:10             ` 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=8335oq4j8z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@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).