From: Per Bothner <per@bothner.com>
To: Claude Marinier <claudem223@gmail.com>, kawa@sourceware.org
Subject: Re: build from svn - texinfo errors
Date: Mon, 18 Apr 2016 20:33:00 -0000 [thread overview]
Message-ID: <57154497.3090307@bothner.com> (raw)
In-Reply-To: <CAPg6usDKWtXCCesnGH11nwWtANpSbhWh4Sc5Av32iXHaoeo4ng@mail.gmail.com>
On 04/18/2016 01:09 PM, Claude Marinier wrote:
> Hi,
>
> After spending hours getting Kawa from the Subversion repository (it
> kept timing-out),
Bummer. I normally don't have problems, but it is possible
there is a server glitch.
> I was able to build it up to the documentation. It
> produces many errors; here are the first few.
>
> Making all in doc
> ...
> kawa.texi:3428: unknown command `sup' (possibly involving @arbno)
> ...
Yes, you can ignore it.
The @sup command was added to texinfo 6.0 (at my suggestion).
(makeinfo --version should be 6.0 or higher.)
Before that I defined @sup as a macro, but that was obviously more of a kludge.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2016-04-18 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 20:09 Claude Marinier
2016-04-18 20:33 ` Per Bothner [this message]
2016-04-22 19:04 ` Claude Marinier
2016-04-22 20:52 ` Per Bothner
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=57154497.3090307@bothner.com \
--to=per@bothner.com \
--cc=claudem223@gmail.com \
--cc=kawa@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).