From: SpiceBug <spicebug/*no_spam*/@freesurf.fr>
Subject: [Oort v0.13] gnus.texi compile error
Date: Tue, 21 Jan 2003 18:45:23 +0100 [thread overview]
Message-ID: <86wukycs7g.fsf@technologist.dyndns.org> (raw)
Hi folks.
While compiling both Oort Gnus v0.12 and 0.13, I got the same error,
given at the bottom of this post.
Once gnus.texi is modified (removed the special tags), everything goes well.
Just for your information.
Regards,
SpiceBug
--------------------------------------------------------------------------
make[1]: Entering directory `/usr/local/src/ognus-0.13/texi'
if test "xmakeinfo" != "xno" ; then \
makeinfo -I . -o gnus gnus.texi; \
else \
rm -f gnus; \
emacs -batch -q -no-site-file -l ./infohack.el -f batch-makeinfo gnus.texi; \
fi
Making info file `gnus' from `gnus.texi'.
gnus.texi:2720: Unknown command `anchor'.
gnus.texi:2720: Misplaced {.
gnus.texi:2720: Misplaced }.
gnus.texi:21211: Unknown command `acronym'.
gnus.texi:21211: Misplaced {.
gnus.texi:21211: Misplaced }.
makeinfo: Removing output file `gnus' due to errors; use --force to preserve.
make[1]: *** [gnus] Error 2
make[1]: Leaving directory `/usr/local/src/ognus-0.13/texi'
make: *** [info] Error 2
next reply other threads:[~2003-01-21 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 17:45 SpiceBug [this message]
[not found] ` <m3znpuz97d.fsf@quimbies.gnus.org>
2003-01-22 18:02 ` faust
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=86wukycs7g.fsf@technologist.dyndns.org \
--to=spicebug/*no_spam*/@freesurf.fr \
/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).