<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">09.11.2023 12:10, Michael Van Canneyt
via fpc-devel пишет:<br>
</div>
<blockquote type="cite"
cite="mid:3ec66b4-6316-1ec8-f225-13cc921a70@freepascal.org">
<br>
<br>
On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote:
<br>
<br>
<blockquote type="cite">03.11.2023 17:34, Michael Van Canneyt via
fpc-devel пишет:
<br>
<blockquote type="cite">
<br>
<br>
On Fri, 3 Nov 2023, Maxim Ganetsky via fpc-devel wrote:
<br>
<br>
<blockquote type="cite">03.11.2023 17:05, Michael Van Canneyt
via fpc-devel пишет:
<br>
<blockquote type="cite">
<br>
<br>
On Fri, 3 Nov 2023, Maxim Ganetsky via fpc-devel wrote:
<br>
<br>
<blockquote type="cite">Hello.
<br>
<br>
Currently builds in FPC Build repository are failing for
FPC main branch:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://gitlab.com/freepascal.org/fpc/build/-/pipelines">https://gitlab.com/freepascal.org/fpc/build/-/pipelines</a>
<br>
</blockquote>
<br>
I am aware. I cannot build the docs myself.
<br>
<br>
The problem is:
<br>
<br>
Recently the documentation became too big for pdfLaTeX to
handle, too many
<br>
identifiers. (well over 2500 pages)
<br>
<br>
I have not (yet) found a way to increase TexLive's memory
bounds.
<br>
I am investigating this but it seems save_size is stuck at
a value of 80000.
<br>
<br>
So unless I find a solution, either I need to split up the
docs, or completely abandon the idea of PDF docs for the
API reference.
<br>
<br>
For the moment, simply disable the building of the PDF
docs.
<br>
</blockquote>
The problem is, in our CI we rely on precompiled FPC
snapshot TAR installers in order to save time when updating
an image. So no new installer, no new FPC.
<br>
</blockquote>
<br>
Well, all I can say is that I am looking into it.
<br>
<br>
Till a solution is found, you'll need to be patient...
<br>
</blockquote>
<br>
Is there any estimation how much will it take to be fixed?
<br>
</blockquote>
<br>
No, since I don't even know yet what the fix is.
<br>
<br>
<blockquote type="cite">
<br>
If it will take too long, I would like to suggest to temporarily
disable generation of documentation in order to have binary
snapshots available again.
<br>
</blockquote>
<br>
That is what I proposed in the first place.
<br>
<br>
But I have no idea who generates the snapshots you use, or how
they are
<br>
generated.
</blockquote>
<p>In this file:</p>
<p><a class="moz-txt-link-freetext" href="https://gitlab.com/freepascal.org/fpc/build/-/blob/main/.gitlab-ci.yml?ref_type=heads">https://gitlab.com/freepascal.org/fpc/build/-/blob/main/.gitlab-ci.yml?ref_type=heads</a></p>
<p>comment out (add `#` at line start) lines 20, 21, 26-30.</p>
<p>Note that these changes may not be optimal. I see that Florian
wrote this script, so it would be best if he will look at it.</p>
<p>On a side note.</p>
<p>Here:</p>
<p><a class="moz-txt-link-freetext" href="https://gitlab.com/freepascal.org/fpc/build/-/jobs/5498828229">https://gitlab.com/freepascal.org/fpc/build/-/jobs/5498828229</a><br>
</p>
<p>I see the following errors:</p>
<div class="js-log-line log-line"><font face="monospace"><span
class="gl-white-space-pre-wrap">Parser error:
../fpcsrc/rtl/linux/osdefs.inc (34,47):
../fpcsrc/rtl/linux/osdefs.inc(34,47) : "identifier" expected,
but "EOF" found</span></font></div>
<div class="js-log-line log-line"></div>
<code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Ignoring error, continuing
with next unit (if any).</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Error: Access violation</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Ignoring error, continuing
with next unit (if any).</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Parser error:
../fpcsrc/rtl/linux/osdefs.inc (34,47):
../fpcsrc/rtl/linux/osdefs.inc(34,47) : "identifier" expected,
but "EOF" found</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Ignoring error, continuing
with next unit (if any).</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Error: Access violation</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Ignoring error, continuing
with next unit (if any).</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Parser error:
/builds/freepascal.org/fpc/build/fpcsrc/packages/rtl-extra/src/linux/osdefs.inc
(38,47):
/builds/freepascal.org/fpc/build/fpcsrc/packages/rtl-extra/src/linux/osdefs.inc(38,47)
: "identifier" expected, but "EOF" found</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Ignoring error, continuing
with next unit (if any).</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Parser error:
/builds/freepascal.org/fpc/build/fpcsrc/rtl/linux/osdefs.inc
(34,47):
/builds/freepascal.org/fpc/build/fpcsrc/rtl/linux/osdefs.inc(34,47)
: "identifier" expected, but "EOF" found</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Ignoring error, continuing
with next unit (if any).</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block">
<div class="js-log-line log-line"><span
class="gl-white-space-pre-wrap">Error: Access violation</span></div>
<div class="js-log-line log-line"></div>
</code><code data-testid="job-log-content" class="job-log d-block"><span
class="gl-white-space-pre-wrap">Ignoring error, continuing with
next unit (if any).</span></code>
<p></p>
<p>So I would think that FPDoc has some problems too. Maybe after
they are fixed, documentation build process will be able finish,
albeit probably with incorrect result. But it will anyway improve
the situation by an order of magnitude.<br>
</p>
<pre class="moz-signature" cols="72">--
Best regards,
Maxim Ganetsky <a class="moz-txt-link-freetext" href="mailto:ganmax@narod.ru">mailto:ganmax@narod.ru</a></pre>
</body>
</html>