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 19:04:49 +0200 [thread overview]
Message-ID: <83mu8qbwwe.fsf@gnu.org> (raw)
In-Reply-To: <0af5b1c9-3ab8-a7e6-36a8-a85a7266d555@gmx.at> (message from martin rudalics on Sun, 8 Mar 2020 17:38:29 +0100)
> Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sun, 8 Mar 2020 17:38:29 +0100
>
> > 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
>
> This doesn't seem to work. Doing that right after a "git pull" triggers
> automatic reconfigure (takes ages here). And after that building fails as
>
> ...
> 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.
> make[1]: Leaving directory `/c/emacs-git/trunk/dbg/lib'
> make: *** [lib] Error 2
> make: *** Waiting for unfinished jobs....
> make[1]: Entering directory `/c/emacs-git/trunk/dbg'
> make -C doc/lispref info
>
>
> If I run your two commands right before "make" it builds normally.
That's what I said: run those before saying "make". 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.
Or maybe you are building outside of the source tree? In that case, I
don't know what you should do.
next prev parent reply other threads:[~2020-03-08 17:04 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 [this message]
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=83mu8qbwwe.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).