Gnus development mailing list
 help / color / mirror / Atom feed
From: Oystein Viggen <oysteivi@tihlde.org>
Subject: texi build error in current CVS
Date: Tue, 26 Oct 2004 16:48:04 +0200	[thread overview]
Message-ID: <03r7nlwn6j.fsf@msgid.viggen.net> (raw)

Hi,

I don't think I've seen this error before:

cd texi && make EMACS="emacs" all
make[1]: Entering directory `/home/xdrift/oysteivi/cvs/gnus/texi'
if test "xmakeinfo" != "xno" ; then \
  makeinfo -I . --enable-encoding -o gnus gnus.texi; \
else \
  rm -f gnus; \
  emacs -batch -q -no-site-file -l ./infohack.el -f batch-makeinfo gnus.texi; \
fi
gnus.texi:11: Unknown command `copying'.
gnus.texi:34: Unmatched `@end'.
gnus.texi:330: Unknown command `insertcopying'.
makeinfo: Removing output file `gnus' due to errors; use --force to preserve.
make[1]: *** [gnus] Error 2
make[1]: Leaving directory `/home/xdrift/oysteivi/cvs/gnus/texi'
make: *** [info] Error 2

This is in current CVS on a Debian woody (current stable) system.
I don't really know texinfo, so I didn't pursue the problem further..

Øystein
-- 
This message was generated by a horde of attack elephants armed with PRNGs.



             reply	other threads:[~2004-10-26 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 14:48 Oystein Viggen [this message]
2004-10-26 15:16 ` Romain Francoise
2004-10-26 22:15   ` Katsumi Yamaoka
2004-10-27  7:43     ` Oystein Viggen

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=03r7nlwn6j.fsf@msgid.viggen.net \
    --to=oysteivi@tihlde.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 NNTP newsgroup(s).