Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2023-11

Build failure in FPC Build repository

16 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Maxim Ganetsky

Hello.

Currently builds in FPC Build repository are failing for FPC main branch:

https://gitlab.com/freepascal.org/fpc/build/-/pipelines

It prevents from updating to the latest FPC 3.3.1 in Lazarus CI build image (it still contains FPC from 01.11.2023) which is needed by latest changes in Lazarus.

Relevant log excerpt:

Transcript written on tcrb1000.log.
|
mktexpk:
/root/.texlive2020/texmf-var/fonts/pk/ljfour/jknappen/ec/tcrb1000.600pk: successfully generated.
||
Input index file dist/pdf/user.idx not found.
||
Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...]
||
make[2]: [Makefile:2602: dist/pdf/user.pdf] Error 1 (ignored) ||
Index style file ./index not found.
||
Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...]
||
system returned with code 256
||
Index style file ./index not found.
||
Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...]
||
system returned with code 256
||
Input index file dist/pdf/user.idx not found.
||
Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...]
||
make[2]: [Makefile:2602: dist/pdf/user.pdf] Error 1 (ignored) ||
Index style file ./index not found.
||
Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...]
||
system returned with code 256
||
Index style file ./index not found.
||
Usage: makeindex [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...]
||
system returned with code 256
||
[#rtl.sysutils.TSymLinkRec] Warning: Target ID of <printshort> is unknown: ""
||
[#rtl.sysutils.TSymLinkRec] Warning: Target ID of <printshort> is unknown: ""
||
[#rtl.sysutils.TSymLinkRec] Warning: Target ID of <printshort> is unknown: ""
||
[#rtl.sysutils.TSymLinkRec] Warning: Target ID of <printshort> is unknown: ""
||
[#rtl.sysutils.TSymLinkRec] Warning: Target ID of <printshort> is unknown: ""
||
[#rtl.sysutils.TRawbyteSymLinkRec] Warning: Target ID of <printshort> is unknown: "TRawbyteSymLinkRec.Mode"
||
[#rtl.sysutils.TUnicodeSymLinkRec] Warning: Target ID of <printshort> is unknown: "TRawbyteSymLinkRec.Mode"
||
Package: #rtl - Documentation process finished.
||
make[2]: *** [Makefile:2602: dist/pdf/rtl.pdf] Error 1 ||
make[1]: *** [Makefile:2165: fpc_zipinstall] Error 2 ||
make: *** [Makefile:3161: pdfzip] Error
|

Best regards, Maxim

Reply by email

Michael Van Canneyt
to Maxim Ganetsky
Maxim Ganetsky wrote 5 lines
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.

Michael.

Reply by email

Maxim Ganetsky
to Michael Van Canneyt

03.11.2023 17:05, Michael Van Canneyt via fpc-devel пишет:

Show quoted text 27 lines
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.

Best regards, Maxim Ganetsky

Reply by email

Michael Van Canneyt
to Maxim Ganetsky
Maxim Ganetsky wrote 31 lines
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...

Michael.

Reply by email

Maxim Ganetsky
to Michael Van Canneyt

03.11.2023 17:34, Michael Van Canneyt via fpc-devel пишет:

Show quoted text 39 lines
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...

I understand, thanks. It is amazing to see how big FPC project has become so it triggers limitations in well established external tools. :)

Best regards, Maxim Ganetsky

Reply by email

Michael Van Canneyt
to Maxim Ganetsky
Maxim Ganetsky wrote 11 lines
>>> 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... I understand, thanks. It is amazing to see how big FPC project has become so it triggers limitations in well established external tools. :)

Indeed.

I recently added TPlatforms in SysUtils for Delphi compatibility.

In Delphi, this set has max 4 elements and can be used as a published property. (and it is used as such in e.g. FMX)

In Free Pascal, this set has max 40+ elements (yes, we support that many platforms), and cannot be used as a published property ! (Max 31 elements allowed)

Such things you only find out the hard way...

Michael.

Reply by email

Maxim Ganetsky
to Michael Van Canneyt: Well, all I can say is that I am looking into it. Till a solution is found, you'll need…

03.11.2023 17:34, Michael Van Canneyt via fpc-devel пишет:

Show quoted text 39 lines
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?

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.

Best regards, Maxim Ganetsky

Reply by email

Michael Van Canneyt
to Maxim Ganetsky
Maxim Ganetsky wrote 42 lines
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.

Michael.

Reply by email

Maxim Ganetsky
to Michael Van Canneyt

09.11.2023 12:10, Michael Van Canneyt via fpc-devel пишет:

Show quoted text 58 lines
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 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

Reply by email

Michael Van Canneyt
to Maxim Ganetsky
Maxim Ganetsky wrote 10 lines
>> 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.

Since the units reference documentation has become too big for LaTeX to handle, I have disabled the generation of PDF for the units reference documentation.

Henceforth, the documentation for the units will only be available as HTML. (and, presumably, chm)

The build should again be OK.

Michael.

Reply by email

Maxim Ganetsky
to Michael Van Canneyt

12.11.2023 19:44, Michael Van Canneyt via fpc-devel пишет:

Show quoted text 25 lines
On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote: >>> 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. Since the units reference documentation has become too big for LaTeX to handle, I have disabled the generation of PDF for the units reference documentation. Henceforth, the documentation for the units will only be available as HTML. (and, presumably, chm) The build should again be OK.

Now FPC 3.3.1 crashes when trying to build cross-compiler for i386-win32:

#7 1175.5 External command "/source-main/compiler/ppcross386 -Twin32 -FUvcl-compat/units/i386-win32/ -Fu/source-main/rtl/units/i386-win32/ -Fu/source-main/packages/fcl-base/units/i386-win32/ -Fu/source-main/packages/rtl-objpas/units/i386-win32/ -Fu/source-main/packages/fcl-xml/units/i386-win32/ -Fu/source-main/packages/fcl-web/units/i386-win32/ -Fu/source-main/packages/fcl-db/units/i386-win32/
-Fu/source-main/packages/rtl-extra/units/i386-win32/ -Fu/source-main/packages/ibase/units/i386-win32/
-Fu/source-main/packages/mysql/units/i386-win32/
-Fu/source-main/packages/odbc/units/i386-win32/
-Fu/source-main/packages/oracle/units/i386-win32/
-Fu/source-main/packages/postgres/units/i386-win32/ -Fu/source-main/packages/sqlite/units/i386-win32/
-Fu/source-main/packages/dblib/units/i386-win32/
-Fu/source-main/packages/pxlib/units/i386-win32/
-Fu/source-main/packages/fcl-json/units/i386-win32/ -Fu/source-main/packages/fcl-fpcunit/units/i386-win32/ -Fu/source-main/packages/paszlib/units/i386-win32/ -Fu/source-main/packages/hash/units/i386-win32/
-Fu/source-main/packages/libtar/units/i386-win32/
-Fu/source-main/packages/fcl-net/units/i386-win32/ -Fu/source-main/packages/fcl-passrc/units/i386-win32/ -Fu/source-main/packages/fcl-process/units/i386-win32/ -Fu/source-main/packages/fcl-hash/units/i386-win32/ -Fu/source-main/packages/fcl-registry/units/i386-win32/ -Fu/source-main/packages/openssl/units/i386-win32/ -Fu/source-main/packages/fastcgi/units/i386-win32/ -Fu/source-main/packages/httpd22/units/i386-win32/ -Fu/source-main/packages/httpd24/units/i386-win32/ -Fu/source-main/packages/winunits-base/units/i386-win32/ -Fu/source-main/packages/libmicrohttpd/units/i386-win32/ -Fu/source-main/packages/rtl-generics/units/i386-win32/ -Fuvcl-compat/src -Fivcl-compat/src -Twin32 -Pi386 -XPi386-win32- -Ur -Xs -O2 -n -di386 -dRELEASE -XX -CX -Sc -viq
vcl-compat/BuildUnit_vcl_compat.pp" failed with exit code 256. Console output:
|
#7 1175.5 Target OS: Win32 for i386
||
#7 1175.5 Compiling vcl-compat/BuildUnit_vcl_compat.pp ||
#7 1175.5 Compiling ./vcl-compat/src/system.permissions.pp ||
#7 1175.5 Compiling ./vcl-compat/src/system.messaging.pp ||
#7 1175.5 Compiling ./vcl-compat/src/system.netencoding.pp ||
#7 1175.5 Writing Resource String Table file: system.netencoding.rsj ||
#7 1175.5 Compiling ./vcl-compat/src/system.ioutils.pp ||
#7 1175.5 Writing Resource String Table file: system.ioutils.rsj ||
#7 1175.5 Compiling ./vcl-compat/src/system.devices.pp ||
#7 1175.5 Compiling ./vcl-compat/src/system.analytics.pp ||
#7 1175.5 Compiling ./vcl-compat/src/system.ansistrings.pp ||
#7 1175.5 system.ansistrings.pp(106,10) Error: Forward declaration not solved "ExtractShortPathName(const AnsiString):System.AnsiString;" ||
#7 1175.5 system.ansistrings.pp(1427) Fatal: There were 1 errors compiling module, stopping
||
#7 1175.5 Fatal: Compilation aborted
||
#7 1175.5
||
#7 1175.5 The installer encountered the following error: ||
#7 1175.5 Compilation of "BuildUnit_vcl_compat.pp" failed ||
#7 1175.5 $0000000000527749
||
#7 1175.5 $00000000005324D8
||
#7 1175.5 $00000000005314B1
||
#7 1175.5 $0000000000532801
||
#7 1175.5 $0000000000535F0A
||
#7 1175.5 $0000000000525F12
||
#7 1175.5 $0000000000526624
||
#7 1175.5 $0000000000479A76
||
#7 1175.5 make[2]: *** [Makefile:1992: smart] Error 1 ||
#7 1175.5 make[2]: Leaving directory '/source-main/packages' ||
#7 1175.5 make[1]: *** [Makefile:3129: packages_smart] Error 2 ||
#7 1175.5 make[1]: Leaving directory '/source-main' ||#7 1175.5 make: *** [Makefile:3283: build-stamp.i386-win32] Error 2|

Best regards, Maxim

Reply by email

Florian Klämpfl
to Michael Van Canneyt: Since the units reference documentation has become too big for LaTeX to handle, I have…
Show quoted text 18 lines
Am 12.11.2023 um 17:44 schrieb Michael Van Canneyt via fpc-devel : On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote: >>> 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. Since the units reference documentation has become too big for LaTeX to handle, I have disabled the generation of PDF for the units reference documentation. Henceforth, the documentation for the units will only be available as HTML. (and, presumably, chm) The build should again be OK.

For the CI it should be no problem. But most installers only come with the PDFs and fixing this properly will be probably a tedious task). Is it possible to split the affected document?

Show quoted text 6 lines
Michael. _______________________________________________ fpc-devel maillist - https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply by email

Michael Van Canneyt
to Florian Klämpfl
Florian Klämpfl wrote 24 lines
> Am 12.11.2023 um 17:44 schrieb Michael Van Canneyt via fpc-devel : > > > > On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote: > >>>> 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. > > Since the units reference documentation has become too big for LaTeX to handle, > I have disabled the generation of PDF for the units reference documentation. > > Henceforth, the documentation for the units will only be available as HTML. > (and, presumably, chm) > > The build should again be OK. For the CI it should be no problem. But most installers only come with the PDFs and fixing this properly will be probably a tedious task). Is it possible to split the affected document?

It is possible, but then 50% of the references are broken...

I need to think how this can be fixed.

Michael.

Reply by email

Michael Van Canneyt
to Maxim Ganetsky: 12.11.2023 19:44, Michael Van Canneyt via fpc-devel пишет: Now FPC 3.3.1 crashes…
Maxim Ganetsky wrote 27 lines
12.11.2023 19:44, Michael Van Canneyt via fpc-devel пишет: > > > On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote: > >>>> 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. > > Since the units reference documentation has become too big for LaTeX to > handle, > I have disabled the generation of PDF for the units reference > documentation. > > Henceforth, the documentation for the units will only be available as HTML. > (and, presumably, chm) > > The build should again be OK. Now FPC 3.3.1 crashes when trying to build cross-compiler for i386-win32:

Oh bloody hell, an IFDEF MSWINDOWS... The IDE didn't create the implementation for that :/

Fixed.

Michael.

Reply by email

Maxim Ganetsky
to Michael Van Canneyt

13.11.2023 0:14, Michael Van Canneyt via fpc-devel пишет:

Show quoted text 35 lines
On Sun, 12 Nov 2023, Maxim Ganetsky via fpc-devel wrote: > 12.11.2023 19:44, Michael Van Canneyt via fpc-devel пишет: >> >> >> On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote: >> >>>>> 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. >> >> Since the units reference documentation has become too big for LaTeX >> to handle, >> I have disabled the generation of PDF for the units reference >> documentation. >> >> Henceforth, the documentation for the units will only be available as >> HTML. >> (and, presumably, chm) >> >> The build should again be OK. > > Now FPC 3.3.1 crashes when trying to build cross-compiler for i386-win32: Oh bloody hell, an IFDEF MSWINDOWS... The IDE didn't create the implementation for that :/

You may want to create an issue.

Fixed.

It is fine now, thanks!

Best regards, Maxim Ganetsky

Reply by email

Michael Van Canneyt
to Maxim Ganetsky
Maxim Ganetsky wrote 38 lines
13.11.2023 0:14, Michael Van Canneyt via fpc-devel пишет: > > > On Sun, 12 Nov 2023, Maxim Ganetsky via fpc-devel wrote: > >> 12.11.2023 19:44, Michael Van Canneyt via fpc-devel пишет: >>> >>> >>> On Thu, 9 Nov 2023, Maxim Ganetsky via fpc-devel wrote: >>> >>>>>> 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. >>> >>> Since the units reference documentation has become too big for LaTeX >>> to handle, >>> I have disabled the generation of PDF for the units reference >>> documentation. >>> >>> Henceforth, the documentation for the units will only be available as >>> HTML. >>> (and, presumably, chm) >>> >>> The build should again be OK. >> >> Now FPC 3.3.1 crashes when trying to build cross-compiler for i386-win32: > > Oh bloody hell, an IFDEF MSWINDOWS... The IDE didn't create the > implementation for that :/ You may want to create an issue.

Well, it's debatable whether it actually should do so. And if so, should the implementation also be in an IFDEF MSWINDOWS ?

I'm inclined to give the IDE the benefit of the doubt :-)

Michael.

Reply by email