I am seeing internal error 2018062911 with trunk r43441 and above. This may be the result of building with DEBUG on, but this configuration normally works fine for me.

Colin

External command "/home/me/fpc/trunk/fpcsrc/compiler/ppcx64 -Tlinux -FUfcl-xml/units/x86_64-linux/
-Fu/home/me/fpc/trunk/fpcsrc/rtl/units/x86_64-linux/ -Fu/home/me/fpc/trunk/fpcsrc/packages/fcl-base/units/x86_64-linux/  -Fu/home/me/fpc/trunk/fpcsrc/packages/fcl-res/units/x86_64-linux/ -Fu/home/me/fpc/trunk/fpcsrc/packages/rtl-objpas/units/x86_64-linux/ -Fu/home/me/fpc/trunk/fpcsrc/packages/iconvenc/units/x86_64-linux/ -Fufcl-xml/src
-Fifcl-xml/src -gl -Ur -Xs -O2 -n -Cg -dx86_64 -dDEBUG -dRELEASE -XX -CX -Sc -S2h -viq fcl-xml/BuildUnit_fcl_xml.pp" failed with exit code 256. Console output:
Target OS: Linux for x86-64
Compiling fcl-xml/BuildUnit_fcl_xml.pp
Compiling ./fcl-xml/src/xmlutils.pp
Compiling ./fcl-xml/src/dom.pp
Compiling ./fcl-xml/src/dtdmodel.pp
Compiling ./fcl-xml/src/dom_html.pp
Compiling ./fcl-xml/src/htmldefs.pp
dom_html.pp(1317,1) Fatal: Internal error 2018062911 Fatal: Compilation aborted

Ooh, thats an oversight on my part.  The internal error is raised as part of the jump optimisations if it finds something other than a label or an alignment hint - I didn't think to check for debug markers.  I'll get around to that right now.  In the meantime, can you raise a bug report over here? https://bugs.freepascal.org - that way, I have somewhere to post a fix.

Is the compiler built with debug features on, or is it just the '-dDEBUG' thing for your own program?

Gareth aka. Kit

Aah, scratch that last question.  The '-gl' flag is more important.

Hi Colin,

So unfortunately I haven't been able to reproduce the issue under Windows, which leads me to believe this issue only crops up when building for Linux.  If you can get on that bug report and tell me what command you're using to build everything (my experience with Linux is not very advanced, but I can navigate it well enough on my virtual machine), then I should be able to track down the unexpected entry that's triggering the internal error and then accommodate for it.

Gareth aka. Kit

Gareth - It is indeed linux 64 bit. I use:

make distclean DEBUG=1 install NOGDB=1 NOGDBMI=1 GDBMI=1 PREFIX=/home/me/usr64 FPC=/home/me/fpc/bootstrap/ppcx64

in the fpcsrc directory

which gives:

make -C fpcsrc distclean
make[1]: Entering directory '/home/me/fpc/trunk/fpcsrc' make -C compiler distclean
make[2]: Entering directory '/home/me/fpc/trunk/fpcsrc/compiler' ..... and crashes after a minute or so as my previous message.

Colin

J. Gareth Moreton wrote

Hi Colin, > > So unfortunately I haven't been able to reproduce the issue under Windows, which leads me to believe this issue only crops up when >

building for Linux. If you can get on that bug report and tell me > what command you're using to build everything (my experience with > Linux is not very advanced, but I can navigate it well enough on my > virtual machine), then I should be able to track down the unexpected > entry that's triggering the internal error and then accommodate for > it. > > Gareth aka. Kit > > _______________________________________________

All fixed,

https://bugs.freepascal.org/view.php?id=36299

Gareth aka. Kit

I can confirm thet the fpc build now works for me (and my application works also).

Thanks for the quick fix

Colin

No problem. Glad to help.

Gareth aka. Kit

On Tue 12/11/19 08:44 , C Western
w.me.uk sent:

I can confirm thet the fpc build now

works for me (and my application

id=36299