Really strange....
Few more things.
Sorry, for this is just trial and error, but I am out of ideas why this error happens in first. (And Lazarus 2.0.0+dfsg-2
aarch64-linux-gtk2 is made by the maintainers of the linux repro, not by anyone from the Lazarus team. So no idea if they did any changes....)
I am assuming you use "Tools > Build ..."?
If you use "make" from the commandline, I do not know if or which of the below steps will work....
1) Since it is Linux, some files are actually in your home folder ~/.lazarus instead of the install dir.
find ~/.lazarus -name fpdebug.ppu
find ~/.lazarus -name fpdbgclasses.ppu
grep fpdebug ~/.lazarus/staticpackages.inc
"fpdbgclasses" is to check for other units from the package.
You can remove it from staticpackages, but as long as it is in the installed list, the IDE will put it back.
If they are in staticpackages.inc, they should go if you uninstall those packages. Try uninstalling them, and "save config", instead of immediate rebuild. See if that remove the packages from staticpackages.
In menu Packages > Package graph, you can see what all requires FpDebug. Any package needing it, must also be removed from the IDE.... (that should be "leakview", and any "LazDebugger*FP*" (with FP in the name).
2) In the other thread, there was a statement to run as root, open the package fpdebug, and compile it.
3)
To get a clean (re)start: Delete the entire ~/.lazarus/ folder.
But if you have settings of your own, backup ~/.lazarus/projectsessions , ~/.lazarus/onlinepackagemanager , ~/.lazarus/lazarus.dci and ~/.lazarus/*.xml
4)
If you do find or manage to produce an fpdebug.ppu and still get the error, then in "Configure build Lazarus" forcefully add the path to it.
-Fu/path_in_which_the_ppu_is
e.g. -Fu/home/you/.lazarus/foo/lib/arch64-gtk/
ONLY use that, if there is no other fpdebug.ppu, but the one to which you point.
Also, if the rebuild succeeds, test if it is needed for further rebuilds, or if the one rebuild fixed the issue and its no longer needed.
Having such path options in your config, can lead to all sorts of issues, as the IDE does not expect them. So only keep, if needed.
According to your picture, there is no "lib" folder in fpdebug. But it may be under ~/.lazarus/
The above step 1 will show.
The compiler output is not what I expected....
In the dialog opened by menu "Tools" > "Configure Build Lazarus" is an input field (memo) "Options". In that field enter: -va
After compile, the pop up menu of the "Messages" window has a sub menu "Copy", the bottom most entry is "Copy All/Original messages to clipboard"
The text should contain thousands of lines like:
[1.172] (10000) Unitsearch: messages.pas
[1.172] (10000) Unitsearch: C:\FPC\fpc_3.0.4\64\def\units\x86_64-win64\httpd22\messages.ppu
[1.172] (10000) Unitsearch: C:\FPC\fpc_3.0.4\64\def\units\x86_64-win64\httpd22\messages.pp
[1.172] (10000) Unitsearch: C:\FPC\fpc_3.0.4\64\def\units\x86_64-win64\httpd22\messages.pas
[1.172] (10000) Unitsearch: C:\FPC\fpc_3.0.4\64\def\units\x86_64-win64\rtl\messages.ppu
[1.172] (10001) PPU Loading C:\FPC\fpc_3.0.4\64\def\units\x86_64-win64\rtl\messages.ppu
[1.172] (MESSAGES) (10002) PPU Name: C:\FPC\fpc_3.0.4\64\def\units\x86_64-win64\rtl\messages.ppu
[1.172] (MESSAGES) (10005) PPU Time: 2019/01/27 00:46:52
[1.172] (MESSAGES) (10003) PPU Flags: 143488
[1.172] (MESSAGES) (10004) PPU Crc: 5AAEE313
[1.172] (MESSAGES) (10004) PPU Crc: C0E0D75A (intfc)
[1.172] (MESSAGES) (10004) PPU Crc: EEFDAD71 (indc)
But actually this may not be needed. It depends, if the "find" from point 1 above, shows a fpdebug.ppu, then -va is needed, because it will tell why the compiler does not use it.
If there is no fpdebug.ppu on your disk, then we do not need -va.
Other possibility.
- Keep the executable "lazarus" file (and maybe "lazbuild")
- Keep the installed fpc
- Download the sources for 2.0.10 from our site
Install the sources in your home folder (E.g. ~/lazarus / But NOT inside the ~/.lazarus folder )
Copy the "lazarus" executable into the sources folder
- delete ~/.lazarus
- make the old Lazarus install folder inaccessible (rename it / later delete it, if the sources should work)
Start lazarus, and rebuild.
Or instead, run "make BIGIDE"from the command line (you may need to google, how to specify your architecture, if it gets it wrong)
I would not expect it to be needed, but:
-You may again have to go and install/uninstall fpdebug related packages via packages > install packages. Try installing them first.
-Potentially also use "open package" again.