Do you also have buster-backports? (that'can be added to /etc/apt/sources.list) That's what I have and may be different from yours.. Since the new video back end this may be a possible cause in the OS.Mmm, I wonder what package could be using this problem in trunk.
deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpiBut I can't imagine something like that screwing up the config-file for components and not anything else.Me neither, but I had display issues.
And what package did you install manually from backport (with -t buster-backports)?But I can't imagine something like that screwing up the config-file for components and not anything else.Me neither, but I had display issues.
pi@raspberrypi:~ $ locale -a
C
C.UTF-8
en_GB.utf8
POSIXroot@space01:~# locale -a
C
C.UTF-8
en_US.utf8
POSIXpi@raspberrypi:~ $ locale
LANG=en_GB.UTF-8
LANGUAGE=
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=root@space01:~# locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
still don't know where the Lazarus IDE takes the component-palette info from.From the package files. Unfortunately I don't have raspberry pi, but you can check if the unit name is correctly read from the lpk file. Just put a breakpoint at procedure "UpdateUnitName" first line, unit packagedefs.pas(packager subfolder). Is the value of FUnitName is already wrong? If yes, then the lpk file(basically an xml) is not parsed correctly for some reason. Perhaps the latest changes to parse doted filenames(like laz.whatever.unit) could cause the issue. But this is just a guess.
I did not install anything specific for Lazarus or fpc. I installed back-ports updates..... That's something completely different. The cause seems Buster.And what package did you install manually from backport (with -t buster-backports)?But I can't imagine something like that screwing up the config-file for components and not anything else.Me neither, but I had display issues.
I think those are for the loaded packages. And those file- and unit-names display correctly (Open Loaded packages).Quotestill don't know where the Lazarus IDE takes the component-palette info from.From the package files. Unfortunately I don't have raspberry pi, but you can check if the unit name is correctly read from the lpk file. Just put a breakpoint at procedure "UpdateUnitName" first line, unit packagedefs.pas(packager subfolder). Is the value of FUnitName is already wrong? If yes, then the lpk file(basically an xml) is not parsed correctly for some reason. Perhaps the latest changes to parse doted filenames(like laz.whatever.unit) could cause the issue. But this is just a guess.
It seems Lazarus (of even FPC) on Intel/Buster/i386 indeed doesn't compile.FPC compiles OK. Lazarus trunk does not. Package install Lazarus? is in repo 1.8.4 but I did not test an install.
For me (and even fpcupdeluxe) it crashes with compiling fpc. The intermediate ppc2 which is created during the process gives a segmentation fault.It seems Lazarus (of even FPC) on Intel/Buster/i386 indeed doesn't compile.FPC compiles OK. Lazarus trunk does not. Package install Lazarus? is in repo 1.8.4 but I did not test an install.
For me (and even fpcupdeluxe) it crashes with compiling fpc. The intermediate ppc2 which is created during the process gives a segmentation fault.Well, the only problem I have is that my builds suddenly favor Russian.
This is current trunk on Debian 10 buster i386.
For me (and even fpcupdeluxe) it crashes with compiling fpc. The intermediate ppc2 which is created during the process gives a segmentation fault.It seems Lazarus (of even FPC) on Intel/Buster/i386 indeed doesn't compile.FPC compiles OK. Lazarus trunk does not. Package install Lazarus? is in repo 1.8.4 but I did not test an install.
This is current trunk on Debian 10 buster i386.
Yikes.I installed a new Raspbiamn on an RPi 4 and upgraded buster on my RPi3's
Just installed trunk on a fresh Debian Stretch 9.9 on RPI 3 and have the same problem.
@Thaddy, how did you compile trunk on RPI?
With what commands and options?
And what start-compiler did you use?
Did you upgrade to buster (with an older stretch) or did you use a fresh install?
(But even with fpcupdeluxe it didn't work. You might think it passes the correct compiler-options)
pi@raspberrypi:~ $ cat test.pas
program test;
uses classes;
var
O: TObject;
begin
O := TObject.Create;
writeln(O.UnitName);
end.
pi@raspberrypi:~ $ ./dev/fpc/bin/fpc test.pas
Free Pascal Compiler version 3.3.1 [2019/08/14] for arm
Copyright (c) 1993-2018 by Florian Klaempfl and others
Target OS: Linux for ARMHF
Compiling test.pas
Linking test
9 lines compiled, 1.5 sec
pi@raspberrypi:~ $ ./test
System
pi@raspberrypi:~ $No name returned indeed. confirmed.What happens if you hover over the TButton in Lazarus (compiled with that FPC version)?
@Thaddy, I am not a Lazarus Guru. I followed the steps in the book I bought.There is not much I can do, but I reported the bug (it is a serious one) on the bugtracker. The mailing list you want is fpc-devel.
So you are now also seeing the issue I have. The IDE is broken and you are not able to add a new event by double-clicking on the components.
I just want the IDE to work on the Pi 4. I want to make sure the system we build is future proof and at this stage I am stuck.
Who from the Lazarus team looks after this. Rik you stated I can add it to a mailing list somewhere but not sure where or should I leave it with you 2 to sort out ;D ?
I just want the IDE to work on the Pi 4. I want to make sure the system we build is future proof and at this stage I am stuck.Trunk versions are considered unstable and might contain bugs. But these bugs are usually responded to very (and i mean VERY) quickly, if they are found. But this one went unnoticed. I'm in the process of checking out at what revision FPC broke for arm (fun to do with a slow-ass rpi3 %)).
@Thaddy how do I remove Lazarus? You gave me the commands for FPC. I just want to make sure I don't miss a step.
Off course, that only works if you installed Lazarus with apt-get.@Thaddy how do I remove Lazarus? You gave me the commands for FPC. I just want to make sure I don't miss a step.
make -s clean all install OPT="-v0" OS_TARGET=linux CPU_TARGET=arm INSTALL_PREFIX=/home/pi/dev/fpc PP=/home/pi/dev/compiler3/ppcarmIn that case, removing it would mean just deleting that directory (including /home/pi/.lazarus which might be created).Revision: 42476
Author: florian
Date: zondag 21 juli 2019 10:28:29
Message:
* more fixes to rtti after attribute branch merging
----
Modified : /trunk/compiler/ncgrtti.pas
Modified : /trunk/compiler/symconst.pas
Modified : /trunk/rtl/inc/dynarr.inc
Modified : /trunk/rtl/inc/rtti.inc
Modified : /trunk/rtl/inc/rttidecl.inc
Modified : /trunk/rtl/objpas/typinfo.pp