From: Glenn Morris <rgm@gnu.org>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: how to build emacs without documentation?
Date: Tue, 13 Aug 2013 11:52:53 -0400 [thread overview]
Message-ID: <snioz9610q.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20130811142715.GA22029@boo.workgroup> (Gregor Zattler's message of "Sun, 11 Aug 2013 16:27:15 +0200")
Gregor Zattler wrote:
> how do I build emacs without building the documentation in the same
> process?
Either try configure --without-makeinfo (though that may fail),
or instead of plain `make' or `make bootstrap', try
make bootstrap-clean
./autogen.sh
./configure [...]
make all
next prev parent reply other threads:[~2013-08-13 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 14:27 how to build emacs without documentation? Gregor Zattler
2013-08-13 15:52 ` Glenn Morris [this message]
[not found] <mailman.3001.1376231269.12400.help-gnu-emacs@gnu.org>
2013-08-13 14:51 ` Stefan Monnier
2013-08-13 15:26 ` Rustom Mody
2013-08-13 16:32 ` Eli Zaretskii
[not found] ` <mailman.3136.1376411515.12400.help-gnu-emacs@gnu.org>
2013-08-14 16:49 ` Stefan Monnier
2013-08-14 17:56 ` 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=snioz9610q.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=help-gnu-emacs@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.
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).