unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <brandelune@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: building the docs
Date: Fri, 17 May 2019 20:54:52 +0900	[thread overview]
Message-ID: <6352428B-7182-4C07-93BE-1C0E7F985430@gmail.com> (raw)
In-Reply-To: <6EA342E6-AB2A-4A18-B2B6-780E4150FC5A@icloud.com>

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]



> On May 17, 2019, at 19:01, 조성빈 <pcr910303@icloud.com> wrote:
> 
> 2019. 5. 16. 오후 3:59, Jean-Christophe Helary <brandelune@gmail.com> 작성:
> 
>>> If not, perhaps something is wrong with texindex or with texi2pdf?
>> 
>> I removed texinfo and reinstalled it. And that's what I get. Since I use brew on macos to manage texinfo and have never tried to install it by hand, I guess that's a recent update from the package that's causing the glitch since I don't seem to remember having such issues in the relatively recent past...
> 
> IIRC, homebrew’s texinfo is a keg-only formula; If you want the executable in the path you should add /usr/local/opt/texinfo/bin.... and I’m pretty sure I (macOS High Sierra) could get my docs right.

I seem to recall that it was the same for me until I found out about those errors. Maybe it's an upgrade in the OS that messed things.


> On May 17, 2019, at 18:30, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> 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.  

Definitely.

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

That makes sense. 

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

Ok, I'll check all that. But considering that I've recently had errors with the libxml2 headers when building emacs all this is probably strongly related.



Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



[-- Attachment #2: Type: text/html, Size: 4887 bytes --]

  reply	other threads:[~2019-05-17 11:54 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
2019-05-17 10:01     ` 조성빈
2019-05-17 11:54       ` Jean-Christophe Helary [this message]
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=6352428B-7182-4C07-93BE-1C0E7F985430@gmail.com \
    --to=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).