From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>, 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:34:08 +0100 [thread overview]
Message-ID: <m3mvex5oan.fsf@gnus.org> (raw)
In-Reply-To: <a0fukpwe92.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 11 Jan 2017 15:08:57 -0500")
Glenn Morris <rgm@gnu.org> writes:
> (Updated Makefile.in triggers re-generation of Makefile via config.status,
> updated rule for lib/Makefile.in triggers generation of nt/gnulib.mk.)
So would that, in general, be the way to make "make" work again
automatically? That is, if you make a change that requires full
regeneration, you should also update Makefile.in?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-01-11 20:34 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
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 [this message]
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
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=m3mvex5oan.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).