From: Paul Eggert <eggert@cs.ucla.edu>
To: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: MinGW build broken with O_CLOEXEC undeclared
Date: Sun, 8 Mar 2020 10:56:37 -0700 [thread overview]
Message-ID: <f096cb81-2237-cfd9-d4b7-456a72126263@cs.ucla.edu> (raw)
In-Reply-To: <5fd8bab6-6d88-9fe2-d001-9c4b70eefca7@gmx.at>
On 3/8/20 10:21 AM, martin rudalics wrote:
> > 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?
Can you fix the problem by removing your build tree, and then creating an empty
directory and running '../emacs/configure ...' again?
> make info-real info-dir
> make[1]: Entering directory `/c/emacs-git/trunk/dbg/lib'
> Makefile:39: *** Recursive variable `am__v_CC_' references itself (eventually). Stop.
You might be able to work around this via 'make AM_DEFAULT_VERBOSITY=1'.
However, this would likely be treating the symptom not the problem.
next prev parent reply other threads:[~2020-03-08 17:56 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
2020-03-08 17:56 ` Paul Eggert [this message]
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=f096cb81-2237-cfd9-d4b7-456a72126263@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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.