Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Nimar Arora <nimar_arora@yahoo.com>
Subject: errors compiling Oort Gnus
Date: 06 Jan 2003 14:35:50 -0800	[thread overview]
Message-ID: <7wzfzs5kit5.fsf@dlsun92.us.oracle.com> (raw)

Hi,

I just downloaded Oort Gnus from www.gnus.org, typed ./configure in the
directory and then make. It seemed to get past byte compiling a bunch of
files and then it died in the texi directory with the following errors.

I have included the output of uname -a and ./configure below to help
analyze the problem. I appreciate any help.

Thanks,

Nimar

make[1]: Leaving directory `/private/narora/local/src/ognus-0.10/lisp'
cd texi && make EMACS="emacs" all
make[1]: Entering directory `/private/narora/local/src/ognus-0.10/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:316: Unknown command `ifnottex'.
gnus.texi:339: Unmatched `@end'.
gnus.texi:2713: Unknown command `anchor'.
gnus.texi:2713: Misplaced `{'.
gnus.texi:2713: Misplaced `}'.
...

Output of uname -a

SunOS dlsun92 5.6 Generic_105181-29 sun4u sparc SUNW,Ultra-60

Output of ./configure --prefix=/private/narora/local

checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... /usr/local/bin/install -c
checking for makeinfo... makeinfo
checking for emacs... emacs
checking if emacs is really XEmacs... no
checking prefix for your Emacs... /usr/local
checking where .elc files should go... $(datadir)/emacs/site-lisp
checking where etc files should go... $(lispdir)/../etc
checking where the TeXinfo docs should go... $(prefix)/info
checking for acceptable URL version... "no"
checking for acceptable W3 version... "no"
checking for latex... /usr/local/bin/latex
checking for available fonts... "no"
configure: creating ./config.status
config.status: creating Makefile
config.status: creating etc/Makefile
config.status: creating lisp/Makefile
config.status: creating texi/Makefile
config.status: creating texi/gnusconfig.tex
config.status: creating texi/ps/Makefile


             reply	other threads:[~2003-01-06 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 22:35 Nimar Arora [this message]
2003-01-07  4:41 ` Lars Magne Ingebrigtsen
2003-01-07  6:04   ` Nimar Arora
     [not found]     ` <m38yxxijc2.fsf@quimbies.gnus.org>
     [not found]       ` <7wzsmw5fo33.fsf@dlsun92.us.oracle.com>
2003-01-07  6:58         ` Lars Magne Ingebrigtsen

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=7wzfzs5kit5.fsf@dlsun92.us.oracle.com \
    --to=nimar_arora@yahoo.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).