all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: MinGW build broken with O_CLOEXEC undeclared
Date: Sun, 8 Mar 2020 03:08:05 -0700	[thread overview]
Message-ID: <bb582607-176d-f43e-b623-667e4737a6a1@cs.ucla.edu> (raw)
In-Reply-To: <8853cfbe-1f05-0cd9-5bad-da1cd013b5d9@gmx.at>

On 3/8/20 1:34 AM, martin rudalics wrote:
>  > Did the MinGW port formerly compile open.c?
> 
> No, AFAICT (on the release branch it doesn't).

It's not an issue of the master vs the release branch; it's an issue of before 
and after commit 5d4cf1fef85bc24bc4cd9705ebb14150263ad707, which added the 
nofollow flag to set-file-times.

>> 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'.



  reply	other threads:[~2020-03-08 10:08 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 [this message]
2020-03-08 15:11       ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bb582607-176d-f43e-b623-667e4737a6a1@cs.ucla.edu \
    --to=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.