emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Ristow <alan@ristow.info>
To: Vincent Breton <emacs-orgmode@presentiel.fr>,
	 Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problems generating the org-mode documentation
Date: Fri, 22 Oct 2021 11:47:01 +0200	[thread overview]
Message-ID: <6d34ac96-1f7f-7431-c30a-a6892a2db9c5@ristow.info> (raw)
In-Reply-To: <0471d39f-9b41-9e0e-1165-efd12621a76b@presentiel.fr>

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

On 10/22/21 08:16, Vincent Breton wrote:
> >/On Oct 18, 2021, at 20:51, Pedro Andres Aranda Gutierrez 
> <paaguti@gmail.com> /
> >/wrote: />/I'm trying to generate the documentation />/./org.texi:17579: TeX capacity exceeded, sorry [input stack size=5000]. //Jean-Christophe Helary reported too the location of the source of 
> trouble identified by /Takesi Ayanokoji.
> I think the trouble with "TeX capacity exceeded" is not a trouble with "make doc", Emacs or Org.
> Probably a trouble with make or TeX environment as for example the size of available RAM.
> I have already met that on Virtual machine with not enough memory for compilation but just enough for installation of the OS.

It has been a few years since I was deep in the guts of TeX and friends, 
but as I recall, that error usually means that something somewhere has 
caused TeX to expand one or more macros in an infinite loop (though 
there can be other causes). It is generally the result of a syntax error 
or a package conflict, but as far as I remember there aren't really any 
packages to conflict during texinfo conversion. Perhaps there are 
conflicts in the toolchain itself (e.g., between the particular versions 
of (La)TeX and texinfo that you are using)?

If you're really motivated to get to the bottom of this, inserting 
"\tracingall" into the TeX code just before the point where the error 
comes up should help. I can't reproduce the problem (see below), so I 
can't do it myself.

> On my system "make doc" generate an error but I found a temporary solution to generate the documentation in PDF.

For what it is worth, I just did a fresh clone of org-mode and 
successfully generated the docs using both "make doc" and "make pdf". I 
used a fully up-to-date TeXLive 2021 and texinfo (v. 6.7) on Ubuntu 21.10.

As a side note, I received the following warning with both "make" commands:


WARNING: No org-loaddefs.el file could be found from where org.el is 
You need to run "make" or "make autoloads" from Org lisp directory

However, building the docs was successful regardless of whether I ran 
"make autoloads" first.


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

  parent reply	other threads:[~2021-10-22  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  6:16 Problems generating the org-mode documentation Vincent Breton
2021-10-22  6:34 ` Pedro Andres Aranda Gutierrez
2021-10-26 15:09   ` Jean-Christophe Helary
2021-10-22  9:47 ` Alan Ristow [this message]
2021-10-22 10:46 ` Hoffmann, Jobst
2021-10-23  4:06   ` Kyle Meyer
2021-10-23  9:55     ` Pedro Andres Aranda Gutierrez
2021-10-23 14:50     ` Max Nikulin
2021-10-22 15:54 ` Max Nikulin
     [not found] <CAO48Bk82nSQeWaxQ=A97BNdc80bbWvpwQwyh=1e-Ag-oS=QbjQ@mail.gmail.com>
2021-10-18 13:12 ` 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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=6d34ac96-1f7f-7431-c30a-a6892a2db9c5@ristow.info \
    --to=alan@ristow.info \
    --cc=emacs-orgmode@gnu.org \
    --cc=emacs-orgmode@presentiel.fr \
    --cc=lists@traduction-libre.org \
    --cc=paaguti@gmail.com \


* 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


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