09.11.2023 12:10, Michael Van Canneyt via fpc-devel пишет:
On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote:
03.11.2023 17:34, Michael Van Canneyt via fpc-devel пишет:
On Fri, 3 Nov 2023, Maxim Ganetsky via fpc-devel wrote:
03.11.2023 17:05, Michael Van Canneyt via fpc-devel пишет:
On Fri, 3 Nov 2023, Maxim Ganetsky via fpc-devel wrote:
Hello.
Currently builds in FPC Build repository are failing for FPC main
branch:
https://gitlab.com/freepascal.org/fpc/build/-/pipelines
I am aware. I cannot build the docs myself.
The problem is:
Recently the documentation became too big for pdfLaTeX to handle,
too many
identifiers. (well over 2500 pages)
I have not (yet) found a way to increase TexLive's memory bounds.
I am investigating this but it seems save_size is stuck at a value
of 80000.
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.
For the moment, simply disable the building of the PDF docs.
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.
Well, all I can say is that I am looking into it.
Till a solution is found, you'll need to be patient...
Is there any estimation how much will it take to be fixed?
No, since I don't even know yet what the fix is.
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.
That is what I proposed in the first place.
But I have no idea who generates the snapshots you use, or how they are
generated.
In this file:
https://gitlab.com/freepascal.org/fpc/build/-/blob/main/.gitlab-ci.yml?ref_type=heads
comment out (add `#` at line start) lines 20, 21, 26-30.
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.
On a side note.
Here:
https://gitlab.com/freepascal.org/fpc/build/-/jobs/5498828229
I see the following errors:
Parser error: ../fpcsrc/rtl/linux/osdefs.inc (34,47):
../fpcsrc/rtl/linux/osdefs.inc(34,47) : "identifier" expected, but "EOF"
found
|
Ignoring error, continuing with next unit (if any).
||
Error: Access violation
||
Ignoring error, continuing with next unit (if any).
||
Parser error: ../fpcsrc/rtl/linux/osdefs.inc (34,47):
../fpcsrc/rtl/linux/osdefs.inc(34,47) : "identifier" expected, but "EOF"
found
||
Ignoring error, continuing with next unit (if any).
||
Error: Access violation
||
Ignoring error, continuing with next unit (if any).
||
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
||
Ignoring error, continuing with next unit (if any).
||
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
||
Ignoring error, continuing with next unit (if any).
||
Error: Access violation
||Ignoring error, continuing with next unit (if any).|
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.
--
Best regards,
Maxim Ganetskymailto:gan...@narod.ru
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
