unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <brandelune@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: building the docs
Date: Fri, 17 May 2019 12:30:35 +0300	[thread overview]
Message-ID: <83k1epbf7o.fsf@gnu.org> (raw)
In-Reply-To: <894A91CC-FDE0-4F05-A85B-282397E0D8AA@gmail.com> (message from Jean-Christophe Helary on Fri, 17 May 2019 17:56:09 +0900)

> From: Jean-Christophe Helary <brandelune@gmail.com>
> Date: Fri, 17 May 2019 17:56:09 +0900
> 
>  Then I cannot reproduce this with a recent master.  I guess it's
>  something related to your installation of TeX or Texinfo.  Does
>  elisp.log say something about the index?
> 
> The only thing that looks like an error is:
> 
> (/Users/suzume/Documents/Code/emacs/doc/lispref/index.texi (Index) [1224]
> No file elisp.fns.
> ) [1225] ) 

That's your problem.  You need to find out why this file is not being
produced.  

> Also, the html version does include the index, only the ps, dvi and pdf don't.

The HTML version doesn't use TeX, the rest of the formats do.

> I just did a new checkout on emacs master, removed/reinstalled texinfo. But I have the same result.
> There must be something trivial that I'm missing... :(

Looks like some problem with Texinfo you are installing, or with TeX
(a separate package), or maybe with Gawk (nowadays texindex is an Awk
script).



  reply	other threads:[~2019-05-17  9:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  6:15 building the docs Jean-Christophe Helary
2019-05-16  6:52 ` Eli Zaretskii
2019-05-16  6:59   ` Jean-Christophe Helary
2019-05-16 13:54     ` Eli Zaretskii
2019-05-17  8:56       ` Jean-Christophe Helary
2019-05-17  9:30         ` Eli Zaretskii [this message]
2019-05-17 10:01     ` 조성빈
2019-05-17 11:54       ` Jean-Christophe Helary
2019-05-18 12:44         ` Jean-Christophe Helary
2019-05-29  6:11           ` Jean-Christophe Helary
2019-05-29 15:04             ` Eli Zaretskii
2019-05-29 23:37               ` Paul Eggert
2019-05-30  1:46                 ` Jean-Christophe Helary

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k1epbf7o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brandelune@gmail.com \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).