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 01:05:55 -0800 [thread overview]
Message-ID: <3a2617d7-9a98-7460-0067-c1227a3131de@cs.ucla.edu> (raw)
In-Reply-To: <a833d41a-f3a0-8c7c-5680-d56dae3fcdc6@gmx.at>
On 3/8/20 12:53 AM, martin rudalics wrote:
> Compiling master is currently broken on my Windows XP (MinGW gcc 4.8.1) as below
>
> ../../lib/futimens.c:31:1: warning: no previous prototype for 'futimens'
> [-Wmissing-prototypes]
> futimens (int fd, struct timespec const times[2])
Yes, I assume this is a consequence of the patch for Bug#39773 being installed.
The MinGW port will need to make sure that futimens and utimensat work,
presumably by breaking apart fdutimens (which is no longer needed).
> ../../lib/open.c:127:49: error: 'O_CLOEXEC' undeclared (first use in this function)
Did the MinGW port formerly compile open.c? If so, why is O_CLOEXEC undeclared
now when it was declared formerly? If not, why is the MinGW port compiling
open.c now?
next prev parent reply other threads:[~2020-03-08 9:05 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 [this message]
2020-03-08 9:34 ` martin rudalics
2020-03-08 10:08 ` Paul Eggert
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
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=3a2617d7-9a98-7460-0067-c1227a3131de@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 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).