Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: faust <urfaust@optushome.com.au>
Subject: Re: [Oort v0.13] gnus.texi compile error
Date: Wed, 22 Jan 2003 18:02:57 +0000	[thread overview]
Message-ID: <16nt2vganec7kk278qon1r9tmavjkm21i0@4ax.com> (raw)
In-Reply-To: <m3znpuz97d.fsf@quimbies.gnus.org>

 Lars Magne Ingebrigtsen <larsi@gnus.org> ,  emitted these fragments:

>SpiceBug <spicebug/*no_spam*/@freesurf.fr> writes:
>> While compiling both Oort Gnus v0.12 and 0.13, I got the same error,
>> given at the bottom of this post.
>
>You need either a very modern texinfo installation, or to use the
>built-in Emacs texinfo formatter.


I am using Xemacs 21.4.11 ( Native Windows TTY Support ) and did not
have that problem with 0.12 or 0.13

On the other hand, 0.13  did complain about PGP and sieve not being
found.

-- 
natsu-gusa ya     / tsuwamono-domo-ga / yume no ato
summer grasses / strong ones          / dreams site
 
Summer grasses,
All that remains
Of soldier's dreams
(Basho trans. Stryk)


      parent reply	other threads:[~2003-01-22 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 17:45 SpiceBug
     [not found] ` <m3znpuz97d.fsf@quimbies.gnus.org>
2003-01-22 18:02   ` faust [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=16nt2vganec7kk278qon1r9tmavjkm21i0@4ax.com \
    --to=urfaust@optushome.com.au \
    /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).