Can't build lazarus trunk

[KodeZwerg]

I tried to build lazarus with fpcupdeluxe. I got the same errors.

I can not confirm but maybe because I am using Windows as my main OS, sitting in front of that OS and used different fpcupdeluxe settings.
At main screen [X] GitLab checked, FPC / Lazarus Version = [stable]
Inside Setup+ screen [X] Auto switch Repo URL (this ensure that really the latest stable is picked at installation)
Back to main screen check if you having install path correct set or adjust it, press on [Install/Update FPC + Lazarus] whenever it should begin.

Used 64bit FPCUPdeluxe V2.2.0n for x86_64-win64-win32
and installed Lazarus 2.2.4 (rev lazarus_2_2_4) FPC 3.2.2 x86_64-win64-win32/win64 with above options successful.
(my system was clean, ie: i did manual deleted files and folders)

[Bogen85]

I tried to build lazarus with fpcupdeluxe. I got the same errors.

I can not confirm but maybe because I am using Windows as my main OS, sitting in front of that OS and used different fpcupdeluxe settings.
At main screen [X] GitLab checked, FPC / Lazarus Version = [stable]
Inside Setup+ screen [X] Auto switch Repo URL (this ensure that really the latest stable is picked at installation)
Back to main screen check if you having install path correct set or adjust it, press on [Install/Update FPC + Lazarus] whenever it should begin.

Used 64bit FPCUPdeluxe V2.2.0n for x86_64-win64-win32
and installed Lazarus 2.2.4 (rev lazarus_2_2_4) FPC 3.2.2 x86_64-win64-win32/win64 with above options successful.
(my system was clean, ie: i did manual deleted files and folders)

What you describe is for building the latest stable?

zoltanleo had run into a problem building tha latest lazarus trunk (Lazarus GitLab main branch)

[KodeZwerg]

I tried to build lazarus with fpcupdeluxe. I got the same errors.

I can not confirm but maybe because I am using Windows as my main OS, sitting in front of that OS and used different fpcupdeluxe settings.
At main screen [X] GitLab checked, FPC / Lazarus Version = [stable]
Inside Setup+ screen [X] Auto switch Repo URL (this ensure that really the latest stable is picked at installation)
Back to main screen check if you having install path correct set or adjust it, press on [Install/Update FPC + Lazarus] whenever it should begin.

Used 64bit FPCUPdeluxe V2.2.0n for x86_64-win64-win32
and installed Lazarus 2.2.4 (rev lazarus_2_2_4) FPC 3.2.2 x86_64-win64-win32/win64 with above options successful.
(my system was clean, ie: i did manual deleted files and folders)

What you describe is for building the latest stable?

zoltanleo had run into a problem building tha latest lazarus trunk (Lazarus GitLab main branch)

Okay I am sorry, at main screen select for FPC / Lazarus Version = [trunk],
but this was not what I had tested,
just to let you know and to be fair to developers if something not working like it should.

[JuhaManninen]

I actually ran into that a few times... (my scripts were just doing a git pull...)
So I finally just changed them to do fresh clones and that stopped happening.

That sounds alarming. I never had problems with "git pull". If you have local modifications then git refuses to pull but there is a clear message about it.
My guess is that "git pull" worked but the build of FPC was not clean for some reason and old compiled code was used. Building + installing FPC is a more complex task than building + running Lazarus.

just to let you know and to be fair to developers if something not working like it should.

FPC trunk + Lazarus trunk, meaning the latest development versions, is a fragile combination.
This time System.UITypes was extended with definitions that used to be in LCL and they had to be forwarded in LCL.

As I am involved with Lazarus development I mostly use the official FPC release provided by Manjaro Linux. No need to spend time solving such build problems.
For the same reason people who follow and maybe participate in FPC development, may want to use Lazarus fixes branch instead of "main".

[Bogen85]

I actually ran into that a few times... (my scripts were just doing a git pull...)
So I finally just changed them to do fresh clones and that stopped happening.

That sounds alarming. I never had problems with "git pull". If you have local modifications then git refuses to pull but there is a clear message about it.
My guess is that "git pull" worked but the build of FPC was not clean for some reason and old compiled code was used. Building + installing FPC is a more complex task than building + running Lazarus.

Yeah, I should revisit my scripts. It his likely something I had done that caused me to run into the problems before.