Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill White <billw@wolfram.com>
Subject: Re: Problem making gnus info file in current CVS
Date: 29 Sep 2000 09:43:18 -0500	[thread overview]
Message-ID: <ruou2az2r95.fsf@g.wolfram.com> (raw)
In-Reply-To: Emerick Rogul's message of "29 Sep 2000 10:32:48 -0400"

On Fri Sep 29 2000 at 09:32, Emerick Rogul <emerick@csa.bu.edu> said:

  > Hi,

  > I get the following error when making the gnus info file in the
  > current CVS.  Does anyone have any idea what's wrong?  Typo
  > somewhere?

  > Making info file `gnus' from `gnus.texi'.
  > ./gnus.texi:16245: Node `GroupLens' missing Up field.
  > makeinfo: Removing output file `gnus' due to errors; use --force to preserve.

I had the same problem. On ShengHuo ZHU's advice, I upgraded my
makeinfo to the latest available and all worked well. Note that
makeinfo is part of the texinfo package, available at
/anonymous@aeneas.mit.edu:/pub/gnu/texinfo/texinfo-4.0.tar.gz

On Wed Sep 27 2000 at 07:20, ShengHuo ZHU <zsh@cs.rochester.edu> said:

  > Bill White <billw@wolfram.com> writes:
  >> 'cvs update; make' at 1043 UTC 27Sep00 gives an error while making
  >> gnus.info:

[...snip same error Emerick reported...]

  > I am not sure whether it is a bug in makeinfo.  Upgrading makeinfo
  > to 4.0 fixes the problem.

  > ShengHuo

Cheers -

bw
-- 
Bill White . billw@wolfram.com . http://members.wri.com/billw



      parent reply	other threads:[~2000-09-29 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-29 14:32 Emerick Rogul
2000-09-29 14:42 ` ShengHuo ZHU
2000-09-29 15:06   ` Emerick Rogul
2000-09-29 14:43 ` Bill White [this message]

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=ruou2az2r95.fsf@g.wolfram.com \
    --to=billw@wolfram.com \
    /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).