From: Glenn Morris <rgm@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 16626@debbugs.gnu.org, Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: bug#16626: 24.3.50; Unable to make bootstrap after building and installing emacs
Date: Sun, 02 Feb 2014 19:13:15 -0500 [thread overview]
Message-ID: <o4vbwxaw9w.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87lhxtfeuo.fsf@igel.home> (Andreas Schwab's message of "Sun, 02 Feb 2014 21:18:23 +0100")
Andreas Schwab wrote:
> Dunno, 'twas just a WAG.
It's your Wife and Girlfriend?
Anyway, moving on...
I think the normal expectation is that `make' will build anything that
`make install' needs. The Emacs build does not work like this: building
the info files is deferred to the install step.
It seems to me that the `all' target should also run the `info' rule.
I know we are supposed to cater to people without makeinfo, but I can't
see how this is a factor here.
But it does not affect releases, where the info files are premade, so no
rush to change this now.
next prev parent reply other threads:[~2014-02-03 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 17:12 bug#16626: 24.3.50; Unable to make bootstrap after building and installing emacs Thierry Volpiatto
2014-02-02 18:54 ` Andreas Schwab
2014-02-02 19:49 ` Glenn Morris
2014-02-02 20:18 ` Andreas Schwab
2014-02-03 0:13 ` Glenn Morris [this message]
2014-02-03 17:47 ` Andreas Schwab
2014-02-02 19:40 ` Glenn Morris
2014-02-02 19:44 ` Glenn Morris
2014-02-03 6:35 ` Thierry Volpiatto
2014-02-03 19:31 ` Glenn Morris
2014-03-21 6:50 ` 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=o4vbwxaw9w.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=16626@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=thierry.volpiatto@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).