From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: Andreas Schwab <schwab@suse.de>, eliz@gnu.org, bob@rattlesnake.com
Subject: Re: Problem building emacs-lisp-intro.dvi.
Date: Wed, 23 Aug 2006 19:11:14 +0000 (UTC) [thread overview]
Message-ID: <m1GFy8A-0004SNC@rattlesnake.com> (raw)
In-Reply-To: <jeac5vquyq.fsf@sykes.suse.de> (message from Andreas Schwab on Wed, 23 Aug 2006 18:26:37 +0200)
> So the question here is whether texi2dvi invokes TeX in a way that
> would find texinfo.tex in a directory mentione in the -I switch.
\input and @include use the same search path.
Thanks! Am I correct in thinking that means I can change
emacs-lisp-intro.texi from
\input ../man/texinfo
to
\input texinfo
and modify emacs/lispintro/Makefile.in
from
TEXI2DVI = texi2dvi
to
TEXI2DVI = texi2dvi -I
TEXI2DVI_INPUTS=$(srcdir)/../man
and from
emacs-lisp-intro.dvi: ${INFO_SOURCES}
$(ENVADD) $(TEXI2DVI) $(srcdir)/emacs-lisp-intro.texi
to
emacs-lisp-intro.dvi: ${INFO_SOURCES}
$(ENVADD) $(TEXI2DVI) $(TEXI2DVI_INPUTS) $(srcdir)/emacs-lisp-intro.texi
?
To test, I will do a distclean, configure, and bootstrap.
--
Robert J. Chassell
bob@rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.rattlesnake.com http://www.teak.cc
next prev parent reply other threads:[~2006-08-23 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 11:19 Problem building emacs-lisp-intro.dvi Lute Kamstra
2006-08-21 14:50 ` Robert J. Chassell
2006-08-21 15:24 ` Lute Kamstra
2006-08-21 19:11 ` Robert J. Chassell
2006-08-21 21:26 ` Lute Kamstra
2006-08-22 0:45 ` Robert J. Chassell
2006-08-22 1:29 ` Eli Zaretskii
2006-08-22 7:53 ` David Kastrup
2006-08-22 10:26 ` Robert J. Chassell
2006-08-22 10:29 ` David Kastrup
2006-08-22 17:51 ` Robert J. Chassell
2006-08-23 15:49 ` Eli Zaretskii
2006-08-23 16:26 ` Andreas Schwab
2006-08-23 19:11 ` Robert J. Chassell [this message]
2006-08-22 10:30 ` Robert J. Chassell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1GFy8A-0004SNC@rattlesnake.com \
--to=bob@rattlesnake.com \
--cc=eliz@gnu.org \
--cc=schwab@suse.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.