From: Vin Shelton <acs@alumni.princeton.edu>
To: zsh-workers@sunsite.dk
Subject: make install errors
Date: Sun, 03 Dec 2006 20:01:14 -0500 [thread overview]
Message-ID: <873b7wqxt1.fsf@alumni.princeton.edu> (raw)
The latest CVS sources give me the following errors when running 'make
install':
/opt/build/zsh-2006-12-03/Doc/infodir//tzsh.texi:24506: Next field of node `Calendar Bugs' not pointed to (perhaps incorrect sectioning?).
/opt/build/zsh-2006-12-03/Doc/infodir//tzsh.texi:24417: This node (Calendar Utility Functions) has the bad Prev.
/opt/build/zsh-2006-12-03/Doc/infodir//tzsh.texi:24417: Next field of node `Calendar Utility Functions' not pointed to (perhaps incorrect sectioning?).
/opt/build/zsh-2006-12-03/Doc/infodir//tzsh.texi:24506: This node (Calendar Bugs) has the bad Prev.
makeinfo: Removing output file `/opt/build/zsh-2006-12-03/Doc/infodir/zsh.info' due to errors; use --force to preserve.
'makeinfo --version' reports:
makeinfo (GNU texinfo) 4.8
This patch seems to take of the problem:
Index: ChangeLog
===================================================================
RCS file: /cvsroot/zsh/zsh/ChangeLog,v
retrieving revision 1.3360
diff -a -u -u -0 -r1.3360 ChangeLog
--- ChangeLog 3 Dec 2006 21:07:17 -0000 1.3360
+++ ChangeLog 4 Dec 2006 00:59:23 -0000
@@ -0,0 +1,5 @@
+2006-12-03 Vin Shelton <acs@xemacs.org>
+
+ * Doc/Zsh/calsys.yo: "Calendar Bugs" node has no previous, but it
+ does have a next.
+
Index: Doc/Zsh/calsys.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/calsys.yo,v
retrieving revision 1.3
diff -a -u -u -r1.3 calsys.yo
--- Doc/Zsh/calsys.yo 1 Dec 2006 12:54:21 -0000 1.3
+++ Doc/Zsh/calsys.yo 4 Dec 2006 00:59:24 -0000
@@ -526,7 +526,7 @@
)
enditem()
-texinode(Calendar Bugs)(Calendar Utility Functions)()(Calendar Function System)
+texinode(Calendar Bugs)()(Calendar Utility Functions)(Calendar Function System)
sect(Bugs)
There is no tt(calendar_delete) function.
HTH,
Vin
reply other threads:[~2006-12-04 1:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=873b7wqxt1.fsf@alumni.princeton.edu \
--to=acs@alumni.princeton.edu \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).