-
Notifications
You must be signed in to change notification settings - Fork 31
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
gnatcoll-core 25.0.0 fails to compile with GNU/gcc GNAT 12 #88
Comments
Hi @sternenseemann, thank you for raising this issue. We'll work on addressing this one as well as the issue you mentioned here. We'll keep you updated! |
The previous code made gnatcoll-core's json package compilation fail with GNAT 12. The bug has been fixed for GNAT >= 13. Related github issue: #88
Hello @sternenseemann, 515db1c should fix the issue. You can now use the |
Thanks! |
With #515db1c, I still have compile error with gcc 11.2. Inspire by the fix, I did a small modification and it compile fine now. It is based on v25.0.0 |
Hello @qunying , thank you for your contribution! Would you like to open a MR with your fix rebased on the master branch? |
Hello @qunying, I did not manage to reproduce the issue you encountered with GCC 11.2. I confirm that without the 515db1c fix, I obtain the following error:
and with the fix, the build works correctly. Could you double check that you reproduce the issue with the fix already merged ? |
At least we are observing the same behavior, good news! |
I'm currently working on updating all AdaCore released packages in NixOS/nixpkgs to their 25.0.0 versions. I've noticed that it isn't possible to build
gnatcoll-core
25.0.0 (from the GitHub release) with GNAT 12.4.0, i.e. gcc.Now compilation fails with an apparent compiler bug, but since GNAT 12 is not the latest version of GNU GNAT (I'll have to look up if it'll even receive bug fixes anymore), I'm wondering if we can possibly work around it on gnatcoll-core's side. GNAT 13 and 14 are not affected, so maybe it's easy to backport a specific patch, but I haven't been able to figure out which yet.
The text was updated successfully, but these errors were encountered: