From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: Build failure in master for GNU: "error: cannot open < lib/../nt/gnulib.mk: No such file or directory"
Date: Wed, 11 Jan 2017 21:52:44 +0200 [thread overview]
Message-ID: <83o9zdcr1v.fsf@gnu.org> (raw)
In-Reply-To: <m3r3495r0b.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 11 Jan 2017 20:35:32 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: acm@muc.de, emacs-devel@gnu.org
> Date: Wed, 11 Jan 2017 20:35:32 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > gnulib.mk is needed to produce Makefile.in, which is needed to produce
> > Makefile, so Makefile cannot detect these things.
>
> There is a Makefile there
No, there's GNUmakefile, which just includes Makefile if that exists
(which it does in this case).
> For instance, if you check in "make"-breaking changes, then you could
> also check in something that has the necessary commands to make "make"
> work again.
I couldn't find a way of doing that without significant changes in our
Makefiles, something for which I had no time, sorry. Running
autogen.sh every once in a while is not a big deal, really.
> We just have to establish some kind of mechanism -- for
> instance, a special directive in the commit message? Or something else.
I don't think I understand what you have in mind. What directive?
next prev parent reply other threads:[~2017-01-11 19:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:22 Build failure in master for GNU: "error: cannot open < lib/../nt/gnulib.mk: No such file or directory" Alan Mackenzie
2017-01-11 17:30 ` Lars Ingebrigtsen
2017-01-11 18:49 ` Eli Zaretskii
2017-01-11 19:35 ` Lars Ingebrigtsen
2017-01-11 19:52 ` Eli Zaretskii [this message]
2017-01-11 20:36 ` Lars Ingebrigtsen
2017-01-11 21:20 ` Andreas Schwab
2017-01-11 20:08 ` Glenn Morris
2017-01-11 20:34 ` Lars Ingebrigtsen
2017-01-11 17:39 ` Kaushal Modi
2017-01-11 17:41 ` Eric Abrahamsen
2017-01-11 17:54 ` Eli Zaretskii
2017-01-11 18:22 ` Alan Mackenzie
2017-01-11 18:43 ` Noam Postavsky
2017-01-11 18:50 ` Eli Zaretskii
2017-01-11 18:57 ` Alan Mackenzie
2017-01-11 19:44 ` Eli Zaretskii
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=83o9zdcr1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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.