Errors when building FPC from source lazarus / 64-FPC development ---------------------------------------------------------------------- Aruna · 2024-10-29 02:13 Hi, I am trying to install lazarus on to a brand new linux system. I am hitting a brick wall and can use some help please. See below, last few lines are the clues. Hopefully someone will see what went wrong? I have been fighting with this a long while am dead tired so going to call it a day. I will see you all in the morning. Thank you 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 aruna@debian:~/lazarus$ make bigidemake -C packager/registrationmake[1]: Entering directory '/home/aruna/lazarus/packager/registration'/usr/bin/rm -f ../units/x86_64-linux/fcllaz.ppu/usr/bin/ppcx64 -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -Fu/usr/lib/fpc/3.2.2/units/x86_64-linux/rtl -FE. -FU../units/x86_64-linux -Cg -Fl/usr/lib/gcc/x86_64-linux-gnu/12 -dx86_64 fcllaz.pasHint: (11030) Start of reading config file /home/aruna/.fpc.cfgHint: (11031) End of reading config file /home/aruna/.fpc.cfgFree Pascal Compiler version 3.2.2 [2021/05/16] for x86_64Copyright (c) 1993-2021 by Florian Klaempfl and others(1002) Target OS: Linux for x86-64(3104) Compiling fcllaz.pas(1008) 21 lines compiled, 0.1 sec(1022) 2 hint(s) issued/usr/bin/cp -f Makefile.compiled ../units/x86_64-linux/fcl.compiledmake[1]: Leaving directory '/home/aruna/lazarus/packager/registration'make -C components lazbuildpackagesmake[1]: Entering directory '/home/aruna/lazarus/components'make -C lazutilsmake[2]: Entering directory '/home/aruna/lazarus/components/lazutils'/usr/bin/rm -f lib/x86_64-linux/lazutils.ppu/usr/bin/ppcx64 -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -Fu../../packager/units/x86_64-linux -Fu/usr/lib/fpc/3.2.2/units/x86_64-linux/rtl -FE. -FUlib/x86_64-linux -Cg -Fl/usr/lib/gcc/x86_64-linux-gnu/12 -dx86_64 lazutils.pasHint: (11030) Start of reading config file /home/aruna/.fpc.cfgHint: (11031) End of reading config file /home/aruna/.fpc.cfgFree Pascal Compiler version 3.2.2 [2021/05/16] for x86_64Copyright (c) 1993-2021 by Florian Klaempfl and others(1002) Target OS: Linux for x86-64(3104) Compiling lazutils.pas(1008) 33 lines compiled, 0.1 sec(1022) 2 hint(s) issued/usr/bin/cp -f Makefile.compiled lib/x86_64-linux/lazutils.compiledmake[2]: Leaving directory '/home/aruna/lazarus/components/lazutils'make -C codetoolsmake[2]: Entering directory '/home/aruna/lazarus/components/codetools'/usr/bin/rm -f units/x86_64-linux/codetools.ppu/usr/bin/ppcx64 -MObjFPC -Sci -O1 -g -gl -l -vewnhibq -Fu. -Fu../../packager/units/x86_64-linux -Fu../lazutils/lib/x86_64-linux -Fu/usr/lib/fpc/3.2.2/units/x86_64-linux/rtl -FE. -FUunits/x86_64-linux -Cg -Fl/usr/lib/gcc/x86_64-linux-gnu/12 -dx86_64 codetools.pasHint: (11030) Start of reading config file /home/aruna/.fpc.cfgHint: (11031) End of reading config file /home/aruna/.fpc.cfgFree Pascal Compiler version 3.2.2 [2021/05/16] for x86_64Copyright (c) 1993-2021 by Florian Klaempfl and others(1002) Target OS: Linux for x86-64(3104) Compiling codetools.pas(1008) 33 lines compiled, 0.1 sec(1022) 2 hint(s) issued/usr/bin/cp -f Makefile.compiled units/x86_64-linux/codetools.compiledmake[2]: Leaving directory '/home/aruna/lazarus/components/codetools'make -C buildintfmake[2]: Entering directory '/home/aruna/lazarus/components/buildintf'/usr/bin/rm -f units/x86_64-linux/buildintf.ppu/usr/bin/ppcx64 -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -Fu../../packager/units/x86_64-linux -Fu../lazutils/lib/x86_64-linux -Fu/usr/lib/fpc/3.2.2/units/x86_64-linux/rtl -FE. -FUunits/x86_64-linux -Cg -Fl/usr/lib/gcc/x86_64-linux-gnu/12 -dx86_64 buildintf.pasHint: (11030) Start of reading config file /home/aruna/.fpc.cfgHint: (11031) End of reading config file /home/aruna/.fpc.cfgFree Pascal Compiler version 3.2.2 [2021/05/16] for x86_64Copyright (c) 1993-2021 by Florian Klaempfl and others(1002) Target OS: Linux for x86-64(3104) Compiling buildintf.pas(1008) 25 lines compiled, 0.1 sec(1022) 2 hint(s) issued/usr/bin/cp -f Makefile.compiled units/x86_64-linux/buildintf.compiledmake[2]: Leaving directory '/home/aruna/lazarus/components/buildintf'make -C lazdebuggers/lazdebuggerintfmake[2]: Entering directory '/home/aruna/l azarus/components/lazdebuggers/lazdebuggerintf'/usr/bin/rm -f lib/x86_64-linux/lazdebuggerintfpackage.ppu/usr/bin/ppcx64 -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -Fu../../../packager/units/x86_64-linux -Fu/usr/lib/fpc/3.2.2/units/x86_64-linux/rtl -FE. -FUlib/x86_64-linux -Cg -Fl/usr/lib/gcc/x86_64-linux-gnu/12 -dx86_64 lazdebuggerintfpackage.pasHint: (11030) Start of reading config file /home/aruna/.fpc.cfgHint: (11031) End of reading config file /home/aruna/.fpc.cfgFree Pascal Compiler version 3.2.2 [2021/05/16] for x86_64Copyright (c) 1993-2021 by Florian Klaempfl and others(1002) Target OS: Linux for x86-64(3104) Compiling lazdebuggerintfpackage.pas(1008) 16 lines compiled, 0.1 sec(1022) 2 hint(s) issued/usr/bin/cp -f Makefile.compiled lib/x86_64-linux/lazdebuggerintf.compiledmake[2]: Leaving directory '/home/aruna/lazarus/components/lazdebuggers/lazdebuggerintf'make -C debuggerintfmake[2]: Entering directory '/home/aruna/lazarus/components/debuggerintf'/usr/bin/rm -f lib/x86_64-linux/debuggerintf.ppu/usr/bin/ppcx64 -MObjFPC -Scghi -O1 -g -gl -l -venibq -vw-h- -vm4046 -Fu. -Fu../../packager/units/x86_64-linux -Fu../lazdebuggers/lazdebuggerintf/lib/x86_64-linux -Fu../lazutils/lib/x86_64-linux -Fu/usr/lib/fpc/3.2.2/units/x86_64-linux/rtl -FE. -FUlib/x86_64-linux -Cg -Fl/usr/lib/gcc/x86_64-linux-gnu/12 -dx86_64 debuggerintf.pasFree Pascal Compiler version 3.2.2 [2021/05/16] for x86_64Copyright (c) 1993-2021 by Florian Klaempfl and others(1002) Target OS: Linux for x86-64(3104) Compiling debuggerintf.pas(3104) Compiling dbgintfprocess.pas(10001) PPU Loading lib/x86_64-linux/process331.ppu(10011) PPU Source: process331.pp not found(10011) PPU Source: processbody.inc not available(10011) PPU Source: unix_process.inc not available(10028) Recompiling process331, checksum changed for /usr/lib/fpc/3.2.2/units/x86_64- linux/rtl/system.ppu/home/aruna/lazarus/components/debuggerintf/dbgint fprocess.pas(18,29) Fatal: (10022) Can't find unit process331 used by DbgIntfProcessFatal: (1018) Compilation abortedmake[2]: *** [Makefile:3471: debuggerintf.ppu] Error 1make[2]: Leaving directory '/home/aruna/lazarus/components/debuggerintf'make[1]: *** [Makefile:1913: lazbuildpackages] Error 2make[1]: Leaving directory '/home/aruna/lazarus/components'make: *** [Makefile:3151: lazbuild] Error 2aruna@debian:~/lazarus$ ---------------------------------------------------------------------- TRon · 2024-10-29 05:10 Can you try making your build with: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i make clean bigide OPT="-Ur" ---------------------------------------------------------------------- dbannon · 2024-10-29 06:05 Yes Aruna, you are tired ! Check the title of this thread ! I have the files needed to make the missing .ppu, thus - Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i dbannon@dell:~/bin/Lazarus/lazarus-lazarus_4_0_RC_1$ ls -l components/debuggerintf/fcl-proc331total 84-rw-r--r-- 1 dbannon dbannon  3853 Oct 22 04:17 pipes331.pp-rw-r--r-- 1 dbannon dbannon  3532 Oct 22 04:17 process331.pp-rw-r--r-- 1 dbannon dbannon 36088 Oct 22 04:17 processbody.inc-rw-r--r-- 1 dbannon dbannon    41 Oct 22 04:17 README.txt-rw-r--r-- 1 dbannon dbannon  1234 Oct 22 04:17 unix_pipes.inc-rw-r--r-- 1 dbannon dbannon 15343 Oct 22 04:17 unix_process.inc-rw-r--r-- 1 dbannon dbannon  1699 Oct 22 04:17 win_pipes.inc-rw-r--r-- 1 dbannon dbannon 11415 Oct 22 04:17 win_process.inc  They are, apparently, imported from FPC331 and are not in a previous Lazarus. Please check you have them. Might be fun to run this too (from there in your Laz dir) - Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i $> find . -iname "process331*" Look after yourself ! Davo ---------------------------------------------------------------------- Aruna · 2024-10-29 10:39 Quote from: TRon on October 29, 2024, 06:10:09 amCan you try making your build with: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i make clean bigide OPT="-Ur" Hello @TRon how are you? I tried what you suggested and that error dissappeard but we have another one now: 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 make[1]: Leaving directory '/home/aruna/lazarus/tools'make -C packager/registrationmake[1]: Entering directory '/home/aruna/lazarus/packager/registration'/usr/bin/rm -f ../units/x86_64-linux/fcllaz.ppu/usr/bin/ppcx64 -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -Fu. -Fu/usr/lib/fpc/3.2.2/units/x86_64-linux/rtl -FE. -FU../units/x86_64-linux -Cg -Fl/usr/lib/gcc/x86_64-linux-gnu/12 -Ur -dx86_64 fcllaz.pasHint: (11030) Start of reading config file /home/aruna/.fpc.cfgHint: (11031) End of reading config file /home/aruna/.fpc.cfgFree Pascal Compiler version 3.2.2 [2021/05/16] for x86_64Copyright (c) 1993-2021 by Florian Klaempfl and others(1002) Target OS: Linux for x86-64(3104) Compiling fcllaz.pas/home/aruna/lazarus/packager/registration/fcllaz.pas(11,3) Fatal: (10022) Can't find unit db used by fcllazFatal: (1018) Compilation abortedmake[1]: *** [Makefile:3471: fcllaz.ppu] Error 1make[1]: Leaving directory '/home/aruna/lazarus/packager/registration'make: *** [Makefile:3112: registration] Error 2 ---------------------------------------------------------------------- TRon · 2024-10-29 10:52 ok, then we need to dive a bit deeper. Form your logs i can see that you have installed Lazarus into your home directory. Your FPC however seems to be a system-wide installation. The question that are relevant: - How did you install Lazarus in case you have done so and how did you install FPC ? - which exact version of Lazarus are you trying to compile ? ---------------------------------------------------------------------- Aruna · 2024-10-29 10:55 Quote from: dbannon on October 29, 2024, 07:05:55 amYes Aruna, you are tired ! Check the title of this thread ! Hi Davo am still trashed and still trying to waking up over here What did I miss on the title of the thread? Quote from: dbannon on October 29, 2024, 07:05:55 amI have the files needed to make the missing .ppu, thus - Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i dbannon@dell:~/bin/Lazarus/lazarus-lazarus_4_0_RC_1$ ls -l components/debuggerintf/fcl-proc331total 84-rw-r--r-- 1 dbannon dbannon  3853 Oct 22 04:17 pipes331.pp-rw-r--r-- 1 dbannon dbannon  3532 Oct 22 04:17 process331.pp-rw-r--r-- 1 dbannon dbannon 36088 Oct 22 04:17 processbody.inc-rw-r--r-- 1 dbannon dbannon    41 Oct 22 04:17 README.txt-rw-r--r-- 1 dbannon dbannon  1234 Oct 22 04:17 unix_pipes.inc-rw-r--r-- 1 dbannon dbannon 15343 Oct 22 04:17 unix_process.inc-rw-r--r-- 1 dbannon dbannon  1699 Oct 22 04:17 win_pipes.inc-rw-r--r-- 1 dbannon dbannon 11415 Oct 22 04:17 win_process.inc  They are, apparently, imported from FPC331 and are not in a previous Lazarus. Please check you have them. I will check.  Davo would you have a cheat-sheet or something similar lying around that provides step-by-step instructions for building? Both fpc from source and laz- ide from source please? I am going to documnet everything and make one once I get this to work. Preferably with links to the source tar or zip to use to build. Quote from: dbannon on October 29, 2024, 07:05:55 amMight be fun to run this too (from there in your Laz dir) - Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i $> find . -iname "process331*" I will search for the missing files thanks. Quote from: dbannon on October 29, 2024, 07:05:55 amLook after yourself ! I am 'stable' now they say my viral load is near undetectable and blood sugar has stabilized to normal after taking metformin. Stop worrying mate am hard to kill, I am just so fed-up of having to take all these darn pills every day but they keep me alive soo.. Listen Davo do me a favour and drop by IRC? Network is Libera and the channel is #pascal. If you have a few minutes and when convenient? Oh this is totally unrelated and way off-topic but who are the core dev's for lazarus? And who are the core dev's for fpc? Or just tell me on IRC? Be well my friend! ---------------------------------------------------------------------- TRon · 2024-10-29 11:01 Quote from: Aruna on October 29, 2024, 11:55:17 amWhat did I miss on the title of the thread? "Errors when building FPC from source" (counter) evidence: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i make bigide Assuming that you are (still) not completely awake: IDE = lazarus, FPC = compiler Good morning ---------------------------------------------------------------------- Aruna · 2024-10-29 11:18 Quote from: TRon on October 29, 2024, 11:52:40 amok, then we need to dive a bit deeper. Form your logs i can see that you have installed Lazarus into your home directory. Your FPC however seems to be a system-wide installation. The question that are relevant: - How did you install Lazarus in case you have done so and how did you install FPC ? - which exact version of Lazarus are you trying to compile ? My hard drive failed @TRon so I plugged in a stand-by I have lying around in case of emergencies and installed Debian 12 onto this disk. Then I downloaded the lazarus source tar from HERE but I forgot this is now a pristine Debian install so when I tried to run make bigide it said I have to run fpcmake first. So I downloaded the fpc source and that started giving trouble which I can't remember what I did now but managed to fix then it choked saying no GTK? I forgot again so installed GTK2 and those errors went away but new ones appeared. So that is how I tried t install FPC and am trying to compile the Lazarus 4.ORC1. Maybe I should just start again from scratch? ---------------------------------------------------------------------- Aruna · 2024-10-29 11:22 Quote from: TRon on October 29, 2024, 12:01:45 pmQuote from: Aruna on October 29, 2024, 11:55:17 amWhat did I miss on the title of the thread? "Errors when building FPC from source" (counter) evidence: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i make bigide Assuming that you are (still) not completely awake: IDE = lazarus, FPC = compiler Good morning  Oh lord I must have been completely out of it last night to have done that lol. My apologies to everyone. And nope am not fully awake yet and yes a very good morning to you as well. ---------------------------------------------------------------------- TRon · 2024-10-29 11:54 Quote from: Aruna on October 29, 2024, 12:18:26 pm... which I can't remember what I did now but managed to fix then it choked saying no GTK? I forgot again so installed GTK2 and those errors went away but new ones appeared. So that is how I tried t install FPC and am trying to compile the Lazarus 4.ORC1. Maybe I should just start again from scratch? That might perhaps be the quickest solution. In case you are in a hurry to get up and running: - remove everything FPC and Lazarus related from your system (don't forget the configuration files and/or directories) - download fpcupdeluxe 2.4.0e from here. You probably want this file. - install dependencies, see FPCUpdeluxe readme section linux - make the downloaded fpcupdeluxe file executable, e.g. chmod u+x "downloaded_file_name" - start FPCUpDeluxe - at top left select a path (where you have enough access rights) where you want to install FPC (f.e."/home//bin/fpc/3.2.2"). - at the left select Free Pascal compiler version 3.2.2 (let's stay safe there) - press the (FPC) only button - drink some coffee when finished you should have a working FPC compiler and which can be started using its created FPC script (in fact you should use that, and only that script though you can copy it around to a more convenient place but it only makes sens eif you ever want to compile things with FPC in a terminal) - then download the lazarus 4.0rc1 sources, f.e. https://gitlab.com/fr eepascal.org/lazarus/lazarus/-/archive/lazarus_4_0_RC_1/lazarus- lazarus_4_0_RC_1.tar.gz to a location where you can build it. - untar the file - cd into the main directory of the untarred file, then: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i make clean all bigide FPC="full path and name to the fpc.sh (it might be named slightly different) script file that was created by fpcupdeluxe"  That should work for you (it does for me, except that I manually build FPC from source using a bootstrap compiler) - Once the make is done, move the resulting build into a location of your liking (f.e. "/home//bin/lazarus/3.4rc1" ) - then in that location, alongside startlazarus and lazarus executable create a file named lazarus.cfg, and add the option --pcp="location of a directory to where you want to store your lazarus configuration" (for howto/info see wiki ) Once done you should be able to start Lazarus without issues. On first startup of lazarus when it asks: - set the name of the compiler to your fpc.sh script that was created by fpcupdeluxe - please ignore the ignorant popup requesters and/or messages telling that this is not the right compiler because the selected file does not start with the correct letters (it is a dumb and misleading message) - when asked for sources, use the directory that fpcupdeluxe created to store the sources of the rtl and fcl That should be about it. Only thing missing is a menu item. You can consult the gnome .desktop file manual for that. ---------------------------------------------------------------------- Aruna · 2024-10-29 14:05 Quote from: TRon on October 29, 2024, 12:54:36 pmQuote from: Aruna on October 29, 2024, 12:18:26 pm... which I can't remember what I did now but managed to fix then it choked saying no GTK? I forgot again so installed GTK2 and those errors went away but new ones appeared. So that is how I tried t install FPC and am trying to compile the Lazarus 4.ORC1. Maybe I should just start again from scratch? That might perhaps be the quickest solution. I used the *.deb filess  @TRon. And installed them in order as Sourceforge says: You need to download and install all three packages fpc-laz, fpc-src and lazarus- project.Install them in order: fpc-laz - the Compiler, useful command line tools, base units and non visual components like database accessfpc-src - the sources of fpc and its packages, needed for code browsinglazarus-project - the IDE, visual components and help files And thank you god everything went smooth this time I used 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 sudo dpkg -i Quote from: TRon on October 29, 2024, 12:54:36 pmIn case you are in a hurry to get up and running: Yes I was actually (I can't remember why now though? This is what happens when you burn the midnight oil and fly by night:) Thank you for taking so much time to investigate also for the clear and detailed instructions. I have a working laz-ide again but I want to start from scratch and document all the possible brick walls one can hit when doing this without the convenience of a package manager. EDIT: Just attached a screenshot for anyone interested. ---------------------------------------------------------------------- Aruna · 2024-10-29 19:31 @TRon and @dbannon Have a look HERE and then HERE ---------------------------------------------------------------------- dbannon · 2024-10-29 23:41 Quote from: Aruna on October 29, 2024, 03:05:53 pm... And nope am not fully awake yet and yes a very good morning to you as well. ... EDIT: Just attached a screenshot for anyone interested. And a good morning to you too (its sort of late-ish morning here now !). Glad its all working.  I'd suggest your problems related to dependencies. But by putting on the deb packages, they resolved dependencies for you. Just be careful, if you remove those debs (and go back to your own build), apt might decide you don't need those dependencies any more. I prefer to manually install them (with apt of course) so they are marked as "user installed" and get left alone. FPC : From the wiki "first install binutils, make, gcc" Lazarus : from my script : gtk2 - libx11-dev libgtk2.0-dev;  Qt5 - libqt5pas-dev (beware of old versions in repo). Aruna _ I don't use IRC. More than happy to talk over PM here however. Or email if you prefer. Davo ---------------------------------------------------------------------- Aruna · 2024-10-29 23:53 Quote from: dbannon on October 30, 2024, 12:41:50 amAnd a good morning to you too (its sort of late-ish morning here now !). Good late-ish morning and it is 19:46 here which is 7:46 PM Quote from: dbannon on October 30, 2024, 12:41:50 amGlad its all working.  I'd suggest your problems related to dependencies. But by putting on the deb packages, they resolved dependencies for you. Just be careful, if you remove those debs (and go back to your own build), apt might decide you don't need those dependencies any more. I prefer to manually install them (with apt of course) so they are marked as "user installed" and get left alone. FPC : From the wiki "first install binutils, make, gcc" Lazarus : from my script : gtk2 - libx11-dev libgtk2.0-dev;  Qt5 - libqt5pas-dev (beware of old versions in repo). Yes me too I got tired of fixing never ending errors. Strange that you fix one and recompile it comes back with a different one Quote from: dbannon on October 30, 2024, 12:41:50 amAruna _ I don't use IRC, too scared I might bump into Joanna. More than happy to talk over PM here however. Or email if you prefer. Listen, just drop by the channel and 'pm' me so I know your there and just 'lurk' without saying anything? No one will know your in there and no one will say anything to you. Give it a try before you decide not to? She is alright ( really, she does not bite:) but then 'i' have a very thick outer layer of skin... watch that video and tell me if 'you' would take all them pills? ---------------------------------------------------------------------- TRon · 2024-10-30 04:58 Quote from: Aruna on October 29, 2024, 11:55:17 amOh this is totally unrelated and way off-topic but who are the core dev's for lazarus? And who are the core dev's for fpc? To keep it simple: - For Free pascal, see here - For Lazarus, see here But, having said that please also realize that there are tens if not hundreds of other people that contribute (or have contributed over the years) to both projects by various means (also to other associated projects such as f.e. the help). It is just that they do not have (or do not want to have) the right to make certain decisions. Quote from: Aruna on October 29, 2024, 03:05:53 pmI have a working laz-ide again but I want to start from scratch and document all the possible brick walls one can hit when doing this without the convenience of a package manager. In case you want to do everything manually then there a few basic steps: for FPC: - get a bootstrap compiler (FPC-downloads, sourceforge) - retrieve the source-code for the compiler version that should be build (git, gitlab, FPC-downloads, sourceforge) - build the compiler with make using the bootstrap compiler - install the freshly build compiler (make) - configure the compiler for user specific setup (fpc.cfg) either manually or by using fpmkcfg - test the compiler for Lazarus: - retrieve the source-code for the IDE version that should be build (git, gitlab, FPC-downloads, sourceforge) - build the IDE with make using your freshly installed compiler - install the freshly build Lazarus (make) - make sure to set/configure the pcp directory - optionally make a (menu) shortcut for your freshly build IDE - test lazarus Explaining each individual step is more complicated and depends on (and/or can depend on) platform, architecture, preferences, future plans and how someone want to have things setup. The most easy way to install is ofc. using the package manager supplied by the OS and use their FPC and Lazarus packages. The downside of that solution is that there is hardly any upgrade path and/or room for personal preferences ad/or customization. Quote from: Aruna on October 29, 2024, 08:31:57 pmHave a look HERE and then HERE Thank you for sharing and the shout-out. Man, you look wasted there (no offense). Please take good care of yourself ! ---------------------------------------------------------------------- marcov · 2024-10-30 10:55 Moderator notice: offtopic IRC messages and follow ups removed after complaints. Please report off topic posts, don't reply to them. ---------------------------------------------------------------------- Aruna · 2024-11-01 13:02 Quote from: TRon on October 30, 2024, 05:58:04 amQuote from: Aruna on October 29, 2024, 11:55:17 amOh this is totally unrelated and way off- topic but who are the core dev's for lazarus? And who are the core dev's for fpc? To keep it simple: - For Free pascal, see here - For Lazarus, see here Hey many thanks.  Quote from: TRon on October 30, 2024, 05:58:04 amBut, having said that please also realize that there are tens if not hundreds of other people that contribute (or have contributed over the years) to both projects by various means (also to other associated projects such as f.e. the help). It is just that they do not have (or do not want to have) the right to make certain decisions. Alright, understood and respected. Quote from: TRon on October 30, 2024, 05:58:04 amQuote from: Aruna on October 29, 2024, 03:05:53 pmI have a working laz-ide again but I want to start from scratch and document all the possible brick walls one can hit when doing this without the convenience of a package manager. In case you want to do everything manually then there a few basic steps: for FPC: - get a bootstrap compiler (FPC-downloads, sourceforge) - retrieve the source-code for the compiler version that should be build (git, gitlab, FPC-downloads, sourceforge) - build the compiler with make using the bootstrap compiler - install the freshly build compiler (make) - configure the compiler for user specific setup (fpc.cfg) either manually or by using fpmkcfg - test the compiler for Lazarus: - retrieve the source-code for the IDE version that should be build (git, gitlab, FPC-downloads, sourceforge) - build the IDE with make using your freshly installed compiler - install the freshly build Lazarus (make) - make sure to set/configure the pcp directory - optionally make a (menu) shortcut for your freshly build IDE - test lazarus Explaining each individual step is more complicated and depends on (and/or can depend on) platform, architecture, preferences, future plans and how someone want to have things setup. The most easy way to install is ofc. using the package manager supplied by the OS and use their FPC and Lazarus packages. The downside of that solution is that there is hardly any upgrade path and/or room for personal preferences ad/or customization. Thank you very much for this. I want to do this 'manually' for a reason, so 'I' learn how and what goes where and why?  Quote from: TRon on October 30, 2024, 05:58:04 amQuote from: Aruna on October 29, 2024, 08:31:57 pmHave a look HERE and then HERE Thank you for sharing and the shout-out. Man, you look wasted there (no offense). Please take good care of yourself ! No offence taken and yes I was quite out-of-it I just wanted to get the video done and sleep   I mean who starts testing a keyboard without turning on the power to the USB-hub first? In my defence I have done worse ) ---------------------------------------------------------------------- Aruna · 2024-11-01 13:03 Quote from: marcov on October 30, 2024, 11:55:44 amModerator notice: offtopic IRC messages and follow ups removed after complaints. Please report off topic posts, don't reply to them. My Apologies @marcov will not happen again! ---------------------------------------------------------------------- dbannon · 2024-11-03 03:33 Aruna, here is my model for installing FPC and Lazarus, its chiefly about being quick and saving disk space.  https://github.com/davidbannon/FPC_Laz_Install I started doing this on VMs initially because I have so many and disk space is an issue. If you want FPC 3.2.4rc1, first you have to FPC322 to build it, and thats slow on a one cpu VM. My model is to have a tar of the compiled binaries and source on hand, untar it from #HOME and it ends up exactly where I want it, under $HOME/bin. Its very quick, resolves dependencies, installs a fpc.cfg. And easily deleted to save disk space before I close the VM. My current script for downloading, building and configuring Lazarus is there too. I have been using these for awhile, but needed to do a lot of clean ups and sanity checks before going public. I do not consider this, in any way, rival to FPCUPDELUXE, it is limited to - 64 bit Linux FPC 3.20, 3.2.2 and 3.2.4rc1 Assumes a reasonably knowledgeable user, and one who wants to know where things are ! Has none of the fine detail or user friendlyness. Right now, its a very convenient way to get the FPC release candidate at least. Davo