From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: MinGW build broken with O_CLOEXEC undeclared
Date: Sun, 08 Mar 2020 17:03:29 +0200 [thread overview]
Message-ID: <83v9ne99dq.fsf@gnu.org> (raw)
In-Reply-To: <a833d41a-f3a0-8c7c-5680-d56dae3fcdc6@gmx.at> (message from martin rudalics on Sun, 8 Mar 2020 09:53:54 +0100)
> From: martin rudalics <rudalics@gmx.at>
> Date: Sun, 8 Mar 2020 09:53:54 +0100
> Cc: Paul Eggert <eggert@cs.ucla.edu>
>
> 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])
> ^
> CC getopt1.o
> CC gettimeofday.o
> CC memmem.o
> CC mempcpy.o
> CC memrchr.o
> CC mkostemp.o
> CC mktime.o
> CC open.o
> ../../lib/open.c: In function 'sys_open':
> ../../lib/open.c:127:49: error: 'O_CLOEXEC' undeclared (first use in this function)
> flags & ~(have_cloexec <= 0 ? O_CLOEXEC : 0), mode);
> ^
> ../../lib/open.c:127:49: note: each undeclared identifier is reported only once for each function it appears in
> make[1]: *** [open.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make[1]: Leaving directory `/c/emacs-git/trunk/dbg/lib'
> make: *** [lib] Error 2
Should be fixed now.
For cleaner results, I suggest to do the following after "git pull"
and before saying "make":
$ rm lib/*.[oa]
$ touch configure.ac lib/gnulib.mk.in
next prev parent reply other threads:[~2020-03-08 15:03 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
2020-03-08 15:03 ` Eli Zaretskii [this message]
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=83v9ne99dq.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).