Latest Lazarus on a PI4 with 64bit version OS - how to install lazarus / 21-General ---------------------------------------------------------------------- xardomain · 2023-07-20 20:23 Hi all, I would like to install the latest Lazarus on a PI4, but on 64 bit version OS. I followed this and it worked as long I have a 32bit OS: https://wiki.freepascal.org/Build_current_FPC_and_Lazarus_for_Raspberr y_Pi_OS I was able to compile the latest version available, Lazarus 2.2.6 with 3.2.2 fpc. Now, I would like to have the same result but with 64 bit OS, I need a ms-sql dockerized and this works only on 64 bit version. Is there available any documentation to follow? TIA Giuseppe Marullo ---------------------------------------------------------------------- DimTim · 2023-07-21 02:04 Have you tried fpcupdeluxe? https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases Personally, when I needed to write a program for the Raspberry Pi, I used cross-compilation. Working on a PC is much more convenient. ---------------------------------------------------------------------- TRon · 2023-07-21 02:46 Quote from: xardomain on July 20, 2023, 10:23:23 pmIs there available any documentation to follow? Best that I was able to find is https://wiki.freepascal.org/Install_on_aarch64_Arch_or_Manjaro but that is by no means a comparison to the page that you linked to. In case you expect a similar approach then by all means do not use the link I posted as that uses another approach. fwiw I find the page you linked to overly complicated (with all respect to the person who wrote it). PS: Are you aware that the page you linked to contains a link to a storage location that has all required files ready for download ? ---------------------------------------------------------------------- rvk · 2023-07-21 08:54 Quote from: xardomain on July 20, 2023, 10:23:23 pmNow, I would like to have the same result but with 64 bit OS, I need a ms-sql dockerized and this works only on 64 bit version. I assume you have a 64 bit OS on the PI4? In that case you can do dpkg --print-architecture to find out what you need to use instead of armhf. (probably arm64 or something) So, if you change everything on that page from armhf to arm64, see how far you get then ---------------------------------------------------------------------- rvk · 2023-07-21 08:54 Quote from: TRon on July 21, 2023, 04:46:42 amfwiw I find the page you linked to overly complicated (with all respect to the person who wrote it). That page explains how to create a .deb package for installation on another computer or vm. It's not meant to be just a bare install explanation. QuoteSave *.deb to another location, to reinstall later if needed or to share with friends: remember this is free software. I usually also just do a bare install on the computer I want it. (although I still need to change my script for rpi to 64 bit OS) ---------------------------------------------------------------------- TRon · 2023-07-21 09:10 Quote from: rvk on July 21, 2023, 10:54:57 amQuote from: TRon on July 21, 2023, 04:46:42 amfwiw I find the page you linked to overly complicated (with all respect to the person who wrote it). That page explains how to create a .deb package for installation on another computer or vm. It's not meant to be just a bare install explanation. Fair enough. Thereby it seems a stand-alone wiki page (I was unable to find any links that link to it) Though I prefer to use an separate FPC installation as imho that is easier to maintain (on the long run). On a sidenote: is that not what fpc-build is for ? creating deb/rpm packages ? Or does Lazarus not have a counterpart for that ? (I am ignorant when it comes to these kind of things as I prefer to do everything by hand(. QuoteI usually also just do a bare install on the computer I want it. (although I still need to change my script for rpi to 64 bit OS) Yeah I also prefer to build directly from git. And I also need to modify my scripts for rpi OS 64 bit but I haven't even been able to find time to actually install/setup the OS (still running 32 bit  ). ---------------------------------------------------------------------- rvk · 2023-07-21 10:53 Quote from: TRon on July 21, 2023, 11:10:05 amOn a sidenote: is that not what fpc-build is for ? creating deb/rpm packages ? Or does Lazarus not have a counterpart for that ? (I am ignorant when it comes to these kind of things as I prefer to do everything by hand(.I can't find fpc-build in the fpc source. But my guess is that's exactly what the script tools/install/create_fpc_deb.sh, mentioned on that wiki page, is for. BUT that script isn't for Raspberry Pi. It's for i386, amd64, powerpc, sparc and arm. But the Raspberry Pi is armhf (result from dpkg --print-architecture). And not the 64 bit OS of RPI is arm64. So something like this fixes this: Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i case "$CPU_TARGET" in  i386)    ppcbin=386;   FPCArch=i386;;  amd64)   ppcbin=x64;   FPCArch=x86_64;;  powerpc) ppcbin=ppc;   FPCArch=powerpc;;  sparc)   ppcbin=sparc; FPCArch=sparc;;  arm)     ppcbin=arm;   FPCArch=arm;;  armhf)   ppcbin=arm;   FPCArch=arm;;  arm64)   ppcbin=arm;   FPCArch=arm;;  *)    echo "$CPU_TARGET is not supported."        exit -1;;esac Quote from: TRon on July 21, 2023, 11:10:05 amAnd I also need to modify my scripts for rpi OS 64 bit but I haven't even been able to find time to actually install/setup the OS (still running 32 bit  ). Yep, exactly the same for me But I find more and more that there are no longer docker images for armhf (armv7). They all target 64 bit now. So I probably bite the bullet soon  (on a Raspberry Pi 4 8GB and 4GB) ---------------------------------------------------------------------- xardomain · 2023-07-21 15:30 Just to give a little bit of context. It is a very long term project, that would allow unattended installations on bare metal machines and will automate what is NOT normally meant to be automated (something like Sikuli Project /MacroScheduler / AutoHotKey on steroids). Just for fun, I was able to run ms-sql on Docker (the project was started on Delphi on windows, go figure) but this requires 64bit os (at least this is what worked for me) on the PI. Clearly it will be a miracle if it could serve for any purpose. Now, I will have to create several machines, one is a server with a gui, and others will either be physical/virtual agents. If the bare metal installation is requested, I will use a cheap frame grabber, keyboard emulators, media emulators (actually a PI zero, it works to share OS images as emulated DVD), remote mains relay for power and such. This is also required for the station that will "record" the base for the automation, using a PI4 with two monitors, on which one will show the HDMI output of the target. think about a macro recorder where the recording is triggered manually step by step. This building blocks will be used as a base to create the Task, and or course some programming glue will need to be added, like decisions, iterations and so on. Like instead to record the mouse click in a screen position, the macro recorder should be told that I want to click on a image. The screen will dim a little, the user for example will select an icon and then the macro recorder will store the selected image, will create the code to click on it sub sequentially and will actually click to go on with the recording. Upon execution (and taking care of the background and so on) it would click on the correct icon even if the desktop is different. Automation language is not defined yet, but I was experimenting with a zipped task that would be autogenerated Lazarus source code that would transferred to the Agent, compiled and executed against the target. I need to have the ability to compile a Lazarus project from a Lazarus executable. This will allow to have agents on windows, linux and so on. Virtual or physical. Agent and target are somewhat "airgapped" in a sense that the agent look at the target's screen to take decisions and use emulated mouse and keyboard to interact, they could interact with any other OS, provided that there is a way to see the screen. If there is a mean to reach the target via network(os running already, IP KVM available) the target could be virtual in a sense that there is no requirement for physical interfacing (like a HDMI frame grabber) and could connect using RDP/SSH/KVM. It is crazy? Well I think few stuff could get crazier than this. Doable? Probably yes but will take a LOT of time. i would like to use the latest Lazarus build available but even using the files, it gets installed but there are problems(unable to locate fpc.cfg even if its there) and and at least another I don't remember. fpcupdelxuxe didn't work either for me. I tried to compile from source from various links but nothing ended up with the latest version of Lazarus and FPC, I am still searching for it. Now I have done three .deb following instructions, and they seem to work. I tried so many times that I need to check what really works and HOW I ended up with the "correct" deb files. Hope it is more clear now why I can't cross compile and such. TIA Giuseppe Marullo ---------------------------------------------------------------------- TRon · 2023-07-21 20:32 Quote from: rvk on July 21, 2023, 12:53:54 pmI can't find fpc-build in the fpc source. It is a separate(d) project, see https://gitlab.com/freepascal.org/fpc/build QuoteBut my guess is that's exactly what the script tools/install/create_fpc_deb.sh, mentioned on that wiki page, is for. BUT that script isn't for Raspberry Pi. It's for i386, amd64, powerpc, sparc and arm. But the Raspberry Pi is armhf (result from dpkg --print-architecture). And not the 64 bit OS of RPI is arm64. My immediate thoughts would be to ask why not and should it not be added then ? After all it is (now) a supported platform. @xardomain: Ah, thank you for the background (very much appreciated). In that case it makes perfect sense to create deb files for easier distribution. I was a bit puzzled at first because usually people try to invent all kind of ways to install Free Pascal/Lazarus and the easiest by far is simply compiling from source (though that requires some technical knowledge). Most issues arise when using the default package manager that the OS supplies if you want to do something out of the ordinary (such as installing multiple versions or upgrade an existing one while the default package manager does not provide it). I was (wrongfully) assuming that you was trying to do something similar. ---------------------------------------------------------------------- xardomain · 2023-07-21 22:57 Hi TRon, I just need a way to install the latest version of Lazarus on the 64bit version of the os. The installation on the 32bit version works. This will be for the server, and hopefully with ms-sql dockerized and this requires 64bits. The agent, could either be a PI (32 or 64bit) and with Lazarus IDE as well. Now, if/when the system will be released, I technically won't need Lazarus IDE on either the server or the agent, just the executables. The only caveat is that the server will send a complete Lazarus project in source form (zipped) to the agent, that will need to compile it and run. So it is easier to think that I will need Lazarus IDE on both the machine types, 64 and 32. I am trying to recreate from scratch the installation I have done, but apparently there are always new problems coming up. Is there any good soul available to test/provide an installation for Lazarus 2.2.6 / FPC 3.2.2 on latest Raspbian 64 bit? TIA Giuseppe Marullo ---------------------------------------------------------------------- TRon · 2023-07-21 23:19 Quote from: xardomain on July 22, 2023, 12:57:27 amIs there any good soul available to test/provide an installation for Lazarus 2.2.6 / FPC 3.2.2 on latest Raspbian 64 bit? On sourceforge you can find both fpc-3.2.2.arm-linux-on-aarch64.tar fpc-3.2.2.aarch64-linux.tar I am not entirely sure about the differences but my guess would be that the first is the 32-bit compiler that runs on 64-bit arm while the second is the real 64-bit compiler. A deb install/creation you seem to be familiar with so I leave that part. If you just want to install then you can run the installer script. After that you can easily build Lazarus from source (see instructions), but it would indeed require some manual modifications to some sort of default configuration so that your build/setup process is not bothered by not being able to locate some files on startup. No idea how the lazarus deb creator you used does that (but you might have a look and copy the relevant bits for your automated install). ---------------------------------------------------------------------- xardomain · 2023-07-21 23:59 Ok, I got news. This didn't work: dpkg -i ./fpc-laz_3.2.2-230710_armhf.deb dpkg -i ./fpc-src_3.2.2-230710_armhf.deb spkg -i ./lazarus-project_2.2.6-0_armhf.deb but this was what I did to install it after a fresh OS install. Yes, I used the history command! to retrieve exact commands: sudo apt install ./fpc-laz_3.2.2-230710_armhf.deb --YES sudo apt install ./fpc-src_3.2.2-230710_armhf.deb --YES sudo apt install ./lazarus-project_2.2.6-0_armhf.deb This has been issued to a new installation (no patching). Compile build and so on works (also running without debugger) The only thing that does not work: - debugging does not work (and prevent the ide from closing). Resetting the debugger make Lazarus quit. - running the application (with debug) from the IDE freeze I got this at first invocation: The project does not write debug info in Dwarf format. The "FpDebug internal Dwarf-debugger" supports only Dwarf And then I have the following choices: -Cancel -Enable Dwarf3 (-gw3) -Enable Dwart2 (-gw) -Enable Dwarf2 with sets I enabled Dwarf3, but debug fails with Error starting process in debugger with fpDebug and with IDE Default Debugger. If I select GDB it does nothing, say debugging but green "play" icon is green. GDB is installed (gdb-10.1-1.7 (64 bit) but OS may need to be updated (gdb is not listed as one to be updated). Just updated and Lazarus icon disappeared. I did reinstall all the three .deb and got back the icon. Debugging still doesn't work. Of course I better fix the debugger else won't be much fun... Giuseppe Marullo ---------------------------------------------------------------------- TRon · 2023-07-22 00:15 Regarding your issues with the debugger. Are you running lazarus 2.2.6 or 3.0rc1c ? Note that a lot of improvements have been made wrt the debugger (in 3.0rc1) and that there are quite a few issues with the (fp) debugger with 2.2.6 (which you might experience right now). In case you are running 3.0Rc1 with fpdebugger then there is a dedicated thread to report issues (https://forum.lazarus.freepascal.org/index.php/topic,63867.0.html) ---------------------------------------------------------------------- xardomain · 2023-07-22 00:23 I am running 2.2.6, thanks. ---------------------------------------------------------------------- ccrause · 2023-07-22 06:26 Quote from: xardomain on July 22, 2023, 01:59:38 amThe project does not write debug info in Dwarf format. The "FpDebug internal Dwarf- debugger" supports only Dwarf And then I have the following choices: -Cancel -Enable Dwarf3 (-gw3) -Enable Dwart2 (-gw) -Enable Dwarf2 with sets I enabled Dwarf3, but debug fails with Error starting process in debugger with fpDebug and with IDE Default Debugger. If I select GDB it does nothing, say debugging but green "play" icon is green. GDB is installed (gdb-10.1-1.7 (64 bit) but OS may need to be updated (gdb is not listed as one to be updated). Just updated and Lazarus icon disappeared. I did reinstall all the three .deb and got back the icon. Debugging still doesn't work. Note that fpdebug only supports Intel/AMD hardware on Linux, not arm/aarch64. Please show the Debugger backend properties for the gdb debugger in Lazarus (Tools | Options | Debugger > Debugger backend).  Also show the Debug Output information after selecting the gdb debugger and trying to run with debugging (View | IDE internals | Debug Output). ---------------------------------------------------------------------- xardomain · 2023-07-22 10:19 >Please show the Debugger backend properties for the gdb debugger in Lazarus (Tools | Options | Debugger > Debugger backend) It says Gdb [GNU debugger (gdb)] >Also show the Debug Output information after selecting the gdb >debugger and trying to run with debugging (View | IDE internals | >Debug Output). Debug output is empty and it show a window saying error starting process in debugger. ---------------------------------------------------------------------- TRon · 2023-07-22 11:49 @xardomain: See attachment picture where the debugger backend properties are located. Don't forget to use the scrollbar to be able to view them all (resizing the window helps) Without this information ccrause (or anyone else for that matter) is not able to help you. ---------------------------------------------------------------------- xardomain · 2023-07-22 12:42 Wops. sorry. Here it is, thanks in advance. ---------------------------------------------------------------------- TRon · 2023-07-22 14:47 Quote from: xardomain on July 22, 2023, 02:42:40 pmHere it is, thanks in advance. Thank you. Have you noticed that you have two image (1 and 3) that are exactly the same ("tre.jpg") ? ---------------------------------------------------------------------- xardomain · 2023-07-22 15:31 Sorry I was in a hurry. Here it is the missing one (uno.jpg) ---------------------------------------------------------------------- ccrause · 2023-07-23 06:21 Quote from: xardomain on July 22, 2023, 12:19:31 pm>Also show the Debug Output information after selecting the gdb >debugger and trying to run with debugging (View | IDE internals | >Debug Output). Debug output is empty and it show a window saying error starting process in debugger. Does the error window have a button to show more detail, and if so what info is shown? To dig deeper into the problem, read this tip for logging GDB errors and attach the debug log after an attempted debug run in Lazarus. ---------------------------------------------------------------------- xardomain · 2023-07-23 14:34 >Does the error window have a button to show more  detail, and if so what info is shown? Nothing, but if I change Type of debug info in Projects/Options/debugger I get this (debugutput.txt). >To dig deeper into the problem, read this tip for logging GDB errors and attach the debug log after an attempted debug run in >Lazarus. Done, this is the Out window after resetting the debugge(debugoutputwhenlogging.txt): Not clear to me how to make it create a log file I setup the LOG_FILE variable with my home/laz.log, but no file gets generated. I redirected the output and this is the result(redirected.txt). ---------------------------------------------------------------------- ccrause · 2023-07-23 15:48 At least the debugger started GDB properly, and GDB could read a bunch of debug info from the executable. The following excerpt from debugoutputwhilelogging.txt suggests that the process being debugged has been interrupted by SIGINT (Ctrl-C), after which the process is terminated: Code: Text  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i <-exec- run>=thread-group-started,id="i1",pid="2496"=thread- created,id="1",group-id="i1"=library-loaded,id="/lib/ld-linux- armhf.so.3",target-name="/lib/ld-linux-armhf.so.3",host-name="/lib/ld- linux-armhf.so.3",symbols-loaded="0",thread-group="i1",ranges=[{from=" 0xf7fbca50",to="0xf7fd9a48"}]^running*running,thread-id="all"(gdb) ~"\nProgram"~" received signal SIGINT, Interrupt.\n"~"0x0000000000000020 in ?? ()\n"*stopped,reason="signal- received",signal-name="SIGINT",signal-meaning="Interrupt",frame={addr= "0x0000000000000020",func="??",args=[],arch="aarch64"},thread- id="1",stopped-threads="all",core="3"(gdb) &"kill\n" It isn't clear though what generated this signal. ---------------------------------------------------------------------- xardomain · 2023-07-30 11:03 Ok, tried again using the precompiled .deb: fpc-laz_3.2.2-220202_arm64.deb fpc-src_3.2.2-220202_arm64.deb lazarus-project_2.2.0-0_arm64.deb From https://wiki.freepascal.org/Build_current_FPC_and_Lazarus_for_Ras pberry_Pi_OS It seems to complete then I got problems locating fpc.cfg but in reality it seems that the fpc compiler does not support arm 64bit: Compiler "/usr/bin/fpc" does not support target aarch64-linux xar@raspberrypi:~ $ fpc -i Error: ppca64 can't be executed, error message: Failed to execute "ppca64", error code: 127 Does it mean that the .deb was created without the mods in the config file to account for arm64 or what? Now, wondering what to do to compile it on the PI with 64bit support, but it seems that not even 32 bit works completely. I tried fpcupdeluxe, but the exe does not execute, I used (fpcupdeluxe-armv6hf-linux) not sure if this is okay or should I use something different. Wondering if anyone could confirm that Lazarus runs fine on a PI4 with 64bit os, either Lazarus 32 or 64bit. Thanks. Giuseppe Marullo ---------------------------------------------------------------------- rca · 2023-07-30 13:05 @xardomain First, you need to verify that you have 64-bit RPi OS installed: Inside the terminal, type: "dpkg --print-architecture" If it shows "arm64", it is ARM 64 Bit. You must use "fpcupdeluxe- aarch64-linux" to install lazarus/fpc inside the RPi4.If it shows "armhf", it is ARM 32 Bit. You have the 32 bit OS version. ---------------------------------------------------------------------- xardomain · 2023-07-30 15:06 >Inside the terminal, type: "dpkg --print-architecture" dpkg --print-architecture arm64 OK, 64bit. >You must use "fpcupdeluxe-aarch64-linux got the right one thanks, it launched. I just pressed Install/update FPC+Lazarus and it worked, debugger included: Version: 2.2.6 Date 2023-07-30 FPC Version: 3.2.2 Revision: 0df75f4 Now what if I would like to automate this? Is it possible to have exactly the same result launching it or something else exclusively from command line? Should I revert to use fpcup or other stuff to automate this? Anyway *many* thanks, almost problem solved. Giuseppe Marullo ---------------------------------------------------------------------- TRon · 2023-07-30 15:06 Quote from: xardomain on July 30, 2023, 01:03:17 pmIt seems to complete then I got problems locating fpc.cfg but in reality it seems that the fpc compiler does not support arm 64bit: You can force a location (name if you prefer) by using fpc -n @/path/and/name/to/your/fpc.cfg the -n option forces to skip using a(ny) default fpc.cfg file QuoteCompiler "/usr/bin/fpc" does not support target aarch64-linux Because fpc seems not be able to locate the actual compiler Quotexar@raspberrypi:~ $ fpc -i Error: ppca64 can't be executed, error message: Failed to execute "ppca64", error code: 127 Error 127: "file not found" Ergo it can't be located by the fpc frontend. Use a path or configure your fpc.cfg file as intended. edit: It is present in the fpc-laz .deb file usr/lib/fpc/3.2.2/ppca64 so am assuming it will by default be located in /usr/lib/fpc/3.2.2/ when you installed the .deb file. edit2: and the post install script from the .deb file creates a fpc.cfg file for you. QuoteWondering if anyone could confirm that Lazarus runs fine on a PI4 with 64bit os, either Lazarus 32 or 64bit. 32 bit applications on a 64 bit OS (being linux) only runs when you have multi-arch installed. Otherwise you are required to cross-compile (which is more difficult to setup correctly than to use multi-arch imho). ---------------------------------------------------------------------- TRon · 2023-07-30 15:25 Quote from: xardomain on July 30, 2023, 05:06:25 pmNow what if I would like to automate this? Is it possible to have exactly the same result launching it or something else exclusively from command line? Should I revert to use fpcup or other stuff to automate this? I would opt for creating the compiler and lazarus from source (but that is just me). But yes, you can use fpcup to use the commandline exclusively to produce the same result(s). What options you should provide fpcup, I have no idea but I would assume there is some documentation or that you can take over some information from fpcupdeluxe (analyze the logs). ---------------------------------------------------------------------- xardomain · 2023-07-31 16:25 I would rather compile from source, I am installing from a plink script that does most of the stuff from windows(!), including Docker with MS-SQL (the reason to have 64 bit os). I set various stuff, like terminal settings, VNC headless resolution and so on to create an automated installation as much as possible. I will add roles to the script, hopefully each different PI will have its needed stuff installed automagically. My problem is that I was unable to find step by step instructions that would work without errors on the PI4. I tried with the sources but it failed to make bigide and complained about fpcmake something: xar@raspberrypi:~/lazarus-main $ make bigide make: -iVSPTPSOTO: No such file or directory Makefile:250: *** The Makefile doesn't support target -, please run fpcmake first.  Stop. xar@raspberrypi:~/lazarus-main $ Now, there is no fpcmake around, so not sure how to proceed. I tried fpcup BUT this covers only FPC, not Lazarus. Then I tried fpclazup, and the process completed. Once launched the IDE, I got the follwing error (see attach): File: /home/xar/.config/fppkg.cfg Error: there is a problem with the Fppkg configuration. (Fppkg reports that the RTL is not installed.) You could try to restore the configuration files automatically, or adapt the configuration file manually. IDE works, compiles, executes and also debug works, but clearly I would solve the error. Giuseppe Marullo ---------------------------------------------------------------------- TRon · 2023-08-01 02:27 Quote from: xardomain on July 31, 2023, 06:25:33 pmMy problem is that I was unable to find step by step instructions that would work without errors on the PI4. Well, there is/are but it seems not for aarch64 in particular. I do not work with .deb files myself but they seem to work as intended. There are some clear instructions that need to be followed, that is all. The author does not condone mentioning the files nor offer support so unfortunately I can't do anything about that. QuoteI tried with the sources but it failed to make bigide and complained about fpcmake something: It seems that the make process is unable to locate the fpc executable try: Code: [Select]make bigide FPC="/path/to/where/your/script/or/executabl e/is/located/with/name/fpc" If that produces the same error then you have not configured fpc as intended as it is unable to locate the pp compiler. I mentioned that before in an earlier post. After you have build the ide you can "install" it to anywhere using: Code: [Select]make install INSTALL_PREFIX="/path/to/where/you/wish/to/install/lazarus" If you "install" that to some temp directory then you can zip it up and distribute it as long as the host setup/configuration is the same/similar. As long as you do not start Lazarus (without --pcp option) that directory will be a pristine Lazarus "install". It (Lazarus) still needs to be configured but I assume that you are savvy enough to use the --pcp option in order to see what (configuration) files are written to it and how to copy them and/or create the contents of these files manually (to match your preference). edit: I forgot to mention one thing that is not portable. In the specified "INSTALL_PREFIX" directory is a drawer named bin with a couple of file-links. You can (should) ignore those. My own Lazarus build script jumbles some directories around so that everything is nicely tucked away in a directory named "lazarus/2.2.6/" (for v2.2.6) which I can use for deployment. QuoteNow, there is no fpcmake around, so not sure how to proceed. Please don't proceed but try anew. QuoteI tried fpcup BUT this covers only FPC, not Lazarus. Building Lazarus is a piece of cake. Compiling and setting up the fpc compiler correctly is the (most) difficult part. I do not fully understand the "fix" some people seem to have to have FPC integrated with Lazarus. Use it both standalone as that ensures that you can always update one or the other and switch between them and doing so more or less with a blink of an eye. QuoteThen I tried fpclazup, and the process completed. Once launched the IDE, I got the follwing error (see attach): Known issue. fixed in Lazarus 3.0rc1 and you can ignore the error. QuoteIDE works, compiles, executes and also debug works, but clearly I would solve the error. As stated above: It has been fixed already. You can't fix it for 2.2.6. ... and btw ... did you tried https://sourceforge.net/projects/freepas cal/files/Linux/3.2.2/fpc-3.2.2.aarch64-linux.tar/download already ? That prevents you from compiling the compiler and setting up the configuration file as the installer script does that for you.