ANN: Arch linux ~ Breakage of gnatstudio package and new alternative

Since the upgrade of python to version 3.14, the gnatstudio and gnatstudio-bin packages result in the gnatstudio binary crashing on startup. I’ve rebuilt the entire gnatstudio package stack, using python 3.14, to no avail. Therefore, I’ve added a ‘gnatstudio-appimage’ package, which uses the appimage supplied in the 2024 github release. The differences from the 2025 release appear negligible.

I hope the python problems will be fixed in the next release but that will not be til May/June, so hopefully the appimage will suffice til then.

Regards.

GNAT Studio release schema has been changed, new version of GNAT Studio/VS Code extenstion will be released each quarter.

Right now GNAT Studio uses Python 3.11.

It is recommended to use prebuild binaries from GitHub.

1 Like

Thank you for the rapid response, godunko.

Quarterly releases of Gnat Studio will be wonderful.

I have been building/running successfully with Python 3.13, since the last 2025 release, using all the projects in the release sources tarball. On Arch, I have no control over which Python version I use. With Arch’s ‘rolling release’ packaging, they can update the python version whenever it becomes available.

The ‘gnatstudio-bin’ package in Arch uses the prebuilt binaries from GitHub. Unfortunately, it also now crashes on startup, after the Python version update.

I’m on Arch and don’t have such problems. But I gave up with all Ada/gnat AUR packages a few years ago as the experience was really painful.

For the toolchain, I used getada and alire from there (as a user not as root). For gnatstudio, I directly use the github binary release and their install script.

1 Like

Okay, I’ve just re-tried installing gnatstudio-bin package (which uses the prebuilt binary from GitHub) … and it works perfectly !

My apologies, Godunko.

I can’t imagine why it failed yesterday, when I tried it. The only difference was a reboot but that should make no difference. I feel like a damned fool.

The gnatstudio package, built from source, still crashes after re-building just now.

$ gnatstudio
Unexpected fatal error, GNAT Studio is in an inconsistent state … then a huge backtrace.

I’m sorry for your pain, that would be my fault. Many AUR ada packages were a mess, a few years ago. They have improved somewhat after using the ‘version consistent’ sources from the github Gnatstudio Github release ‘sources’ tarball. But of course, if your current alire setup is working well, I don’t expect you to revert to the AUR :slight_smile: .

For any others who do use the AUR, if you encounter problems, please report them on the AUR package ‘comments’ section. I try to address them within a few days, at most.

@godunko Just one question: when will the next release arrive? I tried installing it from source several times but it was beyond my capabilities… :frowning:

Could anyone help or give me some guidance on how to install GNATStudio from source on Ubuntu 24.04?

Here are the gnatstudio package dependencies in order of building/installing …

05.0-gnatcoll-core
06.0-gnatcoll-bindings
07.0-gnatcoll-sql
08.0-gnatcoll-db2ada
09.0-gnatcoll-postgres
10.0-gnatcoll-sqlite
11.0-gnatcoll-xref
12.0-gnatcoll-gnatinspect
13.0-ada-libfswatch
14.0-adasat
15.0-libvss
15.5-prettier-ada
16.0-langkit
17.0-gpr2
18.0-libadalang
19.0-templates_parser
20.0-libadalang-tools
24.0-markdown
25.0-gnatdoc
26.0-gtkada
26.5-ada_spawn
26.7-lal-refactor
26.8-gnatformat
27.0-ada_language_server
28.0-gnatstudio

Use the sources from …

https://github.com/AdaCore/gnatstudio/releases/download/gnatstudio-cr-20250417/gnatstudio-sources-x86_64-linux.tar.gz

… as they are all version compatible.

You can also look in the Arch AUR PKGBUILD’s for each package to see possible patches and build/install commands for each package …

Let me know if you hit problems.

Hope this helps.

Given the effort involved, I’d probly take godunko’s advice and just use the prebuilt binary in the latest github release.

Yes, it was something like 4 or 5 years ago. And yes, I won’t change as I think it’s better to decouple the toolchain from the rolling system (same for python development).