From: Werner LEMBERG <wl@gnu.org>
To: emacs-devel@gnu.org
Subject: MAKEINFO variable not honoured
Date: Sat, 01 Jan 2011 13:21:51 +0100 (CET) [thread overview]
Message-ID: <20110101.132151.306582047.wl@gnu.org> (raw)
[revno 102734]
For testing purposes, I have installed the current development
version of makeinfo in /usr/local/bin. Since this isn't ready yet for
production purposes (it's unbearably slow), I configured emacs with
MAKEINFO=/usr/bin/makeinfo ./configure
However, during `make bootstrap', this variable isn't honoured since
the sub-Makefiles in the `doc' subdirectory contain lines like this
MAKEINFO = makeinfo --force -I $(srcdir)
which directly overwrite the MAKEINFO variable.
Below a trivial patch which fixes this.
Werner
======================================================================
--- ./doc/lispref/Makefile.in.old 2011-01-01 12:51:56.000000000 +0100
+++ ./doc/lispref/Makefile.in 2011-01-01 13:18:04.000000000 +0100
@@ -32,7 +32,7 @@
# Directory with emacsver.texi.
emacsdir = $(srcdir)/../emacs
-MAKEINFO = makeinfo --force -I $(emacsdir) -I $(srcdir)
+MAKEINFO = @MAKEINFO@ --force -I $(emacsdir) -I $(srcdir)
TEXI2DVI = texi2dvi
TEXI2PDF = texi2pdf
DVIPS = dvips
--- ./doc/lispintro/Makefile.in.old 2011-01-01 12:51:51.000000000 +0100
+++ ./doc/lispintro/Makefile.in 2011-01-01 13:17:47.000000000 +0100
@@ -28,7 +28,7 @@
# Directory with the (customized) texinfo.tex file.
texinfodir = $(srcdir)/../misc
-MAKEINFO = makeinfo --force -I $(srcdir)
+MAKEINFO = @MAKEINFO@ --force -I $(srcdir)
TEXI2DVI = texi2dvi
TEXI2PDF = texi2pdf
DVIPS = dvips
--- ./doc/emacs/Makefile.in.old 2011-01-01 12:51:51.000000000 +0100
+++ ./doc/emacs/Makefile.in 2011-01-01 13:17:15.000000000 +0100
@@ -39,7 +39,7 @@
# The makeinfo program is part of the Texinfo distribution.
# Use --force so that it generates output even if there are errors.
-MAKEINFO = makeinfo --force -I $(srcdir)
+MAKEINFO = @MAKEINFO@ --force -I $(srcdir)
TEXI2DVI = texi2dvi
TEXI2PDF = texi2pdf
--- ./doc/misc/Makefile.in.old 2011-01-01 12:51:56.000000000 +0100
+++ ./doc/misc/Makefile.in 2011-01-01 13:18:23.000000000 +0100
@@ -42,7 +42,7 @@
# The makeinfo program is part of the Texinfo distribution.
# Use --force so that it generates output even if there are errors.
-MAKEINFO = makeinfo --force -I$(emacsdir)
+MAKEINFO = @MAKEINFO@ --force -I$(emacsdir)
# Also add new entries to INFO_FILES in the top-level Makefile.in.
INFO_TARGETS = \
next reply other threads:[~2011-01-01 12:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 12:21 Werner LEMBERG [this message]
2011-01-03 5:23 ` MAKEINFO variable not honoured Werner LEMBERG
2011-01-03 5:50 ` Glenn Morris
2011-01-03 6:20 ` Werner LEMBERG
2011-01-03 8:22 ` Andreas Schwab
2011-01-03 8:36 ` Werner LEMBERG
2011-01-03 8:50 ` Andreas Schwab
2011-01-03 18:23 ` Werner LEMBERG
2011-01-21 18:36 ` Werner LEMBERG
2011-01-22 16:00 ` Chong Yidong
2011-01-23 10:39 ` Werner LEMBERG
2011-01-23 11:45 ` Eli Zaretskii
2011-01-23 11:57 ` Werner LEMBERG
2011-01-23 12:41 ` Eli Zaretskii
2011-01-23 14:11 ` Werner LEMBERG
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=20110101.132151.306582047.wl@gnu.org \
--to=wl@gnu.org \
--cc=emacs-devel@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).