-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tried building Sparforte with FSF GCC 13 recently? #27
Comments
I have not heard of anyone else reporting these issues. |
Well, until proven otherwise, I'm going to assume that this is reproducible and that nobody with the latest release of GCC (aka FSF gnat) can build sparforte. |
For the record, the new release 2.6.2 also cannot be built by GCC 13 - due to the same GNAT Bug ICE |
Same on Fedora Linux with GCC 13. |
This is one of the top items in the TODO file. The database and graphics packages are two of the largest and oldest components in SparForte and both need to be rebuilt. I understand the issue but I have a full-time job and am a caretaker in my family. I'm limited to about 30 minutes work per week on SparForte right now. Unless some volunteers can assist, the best I can do is temporarily remove the pen package until the issues can be resolved. That will break some of my own projects that use the pen package but it will keep SparForte compiling. |
I just want to point out that a GNAT BUG is a defect in the compiler (Internal Compiler Error). After that, then sure, if alternate code avoids the ICE, then a patch can be provided if not outright change the code. |
Bug report has been submitted. |
Bug report rejected because I have not created a small example. |
GCC will fix ICEs quickly if they they can be reproduced easily, but them saying to "try newer compilers" is not good advice. In my experience, once they introduce a gnat bug, it persist to newer releases. |
I have update the --without-sdl option to not compile any SDL dependencies and have removed the "nosdl" files. The language is passing tests. However, when I try a clean virtual machine with no SDL C libraries present, it builds but when I run it the language is raising exceptions for unknown reasons when running commands. I will continue to investigate. |
I wasn't able to duplicate the exceptions when performing the same build on Rocky Linux. I've released a new version 2.6.3 with the ability to disable SDL through the gnat preprocessor as a workaround for the GCC 13 issues. |
Sparforte currently doesn't build for me since switching from GCC 11.2 to GCC 13.2
The first issue was stopped on a treat-warnings-as-errors here:
I got past that by adding the "-gnatd.E" flag.
But a bit further it crashed again due to a compiler ICE:
The ICE isn't the code's fault but there might be during coding choice that works around it.
In any case I would be interested to hear if these issues can be reproduced by others.
The text was updated successfully, but these errors were encountered: