From: Glenn Morris <rgm@gnu.org>
To: 25372@debbugs.gnu.org
Cc: tino.calancha@gmail.com
Subject: bug#25372: 26.0.50; Cannot rebuild Emacs
Date: Fri, 06 Jan 2017 12:05:29 -0500 [thread overview]
Message-ID: <tz60lsnmp2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83k2a8d3gr.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Jan 2017 09:58:44 +0200")
The top-level Makefile, once it exists, should contain the necessary
logic for rebuilding things. Manual steps should not be needed. Probably
AUTOMAKE_INPUTS should be changed to include both
$(srcdir)/lib/gnulib.mk and $(srcdir)/nt/gnulib.mk (which means that the
variable gnulib_mk isn't needed). Strictly speaking, this was probably
true before as well.
next prev parent reply other threads:[~2017-01-06 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 6:46 bug#25372: 26.0.50; Cannot rebuild Emacs Tino Calancha
2017-01-06 7:58 ` Eli Zaretskii
2017-01-06 17:05 ` Glenn Morris [this message]
2017-01-06 18:01 ` Glenn Morris
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=tz60lsnmp2.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=25372@debbugs.gnu.org \
--cc=tino.calancha@gmail.com \
/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).