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: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: MinGW build broken with O_CLOEXEC undeclared
Date: Sun, 08 Mar 2020 17:11:22 +0200	[thread overview]
Message-ID: <83sgii990l.fsf@gnu.org> (raw)
In-Reply-To: <bb582607-176d-f43e-b623-667e4737a6a1@cs.ucla.edu> (message from Paul Eggert on Sun, 8 Mar 2020 03:08:05 -0700)

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 8 Mar 2020 03:08:05 -0700
> Cc: emacs-devel <emacs-devel@gnu.org>
> 
> >> If not, why is the MinGW port compiling open.c now?
> > 
> > How would I find out?
> 
> Find out why the 'configure' script is executing 'REPLACE_OPEN=1' now, when it 
> didn't do it before that commit. You may need to put some debugging commands 
> into it, e.g., 'echo "got to here" >>/tmp/log'.

lib/open.c is not supposed to be compiled in the MinGW build.



  reply	other threads:[~2020-03-08 15:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08  8:53 MinGW build broken with O_CLOEXEC undeclared martin rudalics
2020-03-08  9:05 ` Paul Eggert
2020-03-08  9:34   ` martin rudalics
2020-03-08 10:08     ` Paul Eggert
2020-03-08 15:11       ` Eli Zaretskii [this message]
2020-03-08 15:03 ` Eli Zaretskii
2020-03-08 16:38   ` martin rudalics
2020-03-08 17:04     ` Eli Zaretskii
2020-03-08 17:09       ` Eli Zaretskii
2020-03-08 18:15         ` martin rudalics
2020-03-08 17:21       ` martin rudalics
2020-03-08 17:56         ` Paul Eggert
2020-03-08 18:15           ` martin rudalics

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=83sgii990l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).