From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: MinGW build broken with O_CLOEXEC undeclared
Date: Sun, 8 Mar 2020 18:21:16 +0100 [thread overview]
Message-ID: <5fd8bab6-6d88-9fe2-d001-9c4b70eefca7@gmx.at> (raw)
In-Reply-To: <83mu8qbwwe.fsf@gnu.org>
>> If I run your two commands right before "make" it builds normally.
>
> That's what I said: run those before saying "make".
Hmm... that's what I tried to do. I did "git pull" and then ran the
two commands. The subsequent "make" triggered the "configure" and the
following implied "make" failed as indicated.
> You _must_ force
> configure re-run, because some of the files I changed affect how Emacs
> is configured.
>
> Are you saying that you still run autogen.sh and configure by hand,
> and only after that run "make"? That's unnecessary.
I occasionally do that when "make" fails for some reason. But not in
the scenario you proposed.
> Or maybe you are building outside of the source tree? In that case, I
> don't know what you should do.
I _am_ building out of the source tree. How else could I obtain my -O3
build on Windows I need for daily work and a -O0 build for debugging or
my >= 7 toolkit builds on GNU/Linux?
martin
next prev parent reply other threads:[~2020-03-08 17:21 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
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 [this message]
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=5fd8bab6-6d88-9fe2-d001-9c4b70eefca7@gmx.at \
--to=rudalics@gmx.at \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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).