Lazarus Release 3.0

[dbannon]

I have a 32 debian 12 VM (Virtual Box) running fine. I use the debian supplied FPC322 and built Lazarus from source, it built and worked first time I tried, no difficulties.

A failure to link is, more often than not, caused by the lack of the dev version of some library. I suggest you have a look at https://wiki.freepascal.org/Installing_Lazarus_on_Linux#Build_Lazarus_from_Source

Davo

[JuhaManninen]

fpcupdeluxe when i tried to install lazarus 2.2.6 with fpc 3.2.2
it appears it-s something with 32 bits and glibc incompatibility

See:
 https://gitlab.com/freepascal.org/fpc/source/-/issues/39295
See also my post in the 3.0RC1 thread:
 https://forum.lazarus.freepascal.org/index.php/topic,63867.msg485901.html#msg485901

Solution: Use an older version of Debian (or MX Linux 21.3) or a recent fixed version of FPC.

[dbannon]

calabs, Juhu, I too have an old eMachine, love it.

It has Debian 12 on it, I brought that up to date, installed the debian repo FPC 322, pulled down the current Lazarus 3.0 source and it built fine.

Code: [Select]

sudo apt update
sudo apt upgrade
sudo apt install fpc
mkdir -p bin/Lazarus/LazConfigs
cd bin/Lazarus
wget https://gitlab.com/freepascal.org/lazarus/lazarus/-/archive/lazarus_3_0/lazarus-lazarus_3_0.zip
unzip lazarus-lazarus_3_0.zip
mv lazarus-lazarus_3_0 lazarus_3_0
cd lazarus_3_0
cat > lazarus.cfg
--pcp=/home/dbannon/bin/Lazarus/LazConfigs/lazarus_3_0
ctrl-D
make bigide
(wait quite a while, poor little atom cpu working hard !)

All good !
(if you follow that set of commands, don't forget, your username is probably not "dbannon".)

Davo

[JuhaManninen]

calabs, Juhu, I too have an old eMachine, love it.
It has Debian 12 on it, I brought that up to date, installed the debian repo FPC 322, pulled down the current Lazarus 3.0 source and it built fine.

You probably have FPC built from a fixes branch instead of the release 3.2.2.
The bug is fixed there.

[dbannon]

You probably have FPC built from a fixes branch instead of the release 3.2.2.
The bug is fixed there.

My guess is that Debian, in particular, Abou, has patched it. They don't take ~fixes but do patch particular problems. The FPC in bookworm is at patch level 20 (Bookworm-backports is at 32, but my report above is NOT using backports).

Thus my suggestion that anyone using a Debian based distro probably should just use the disto FPC but build Lazarus from source.

I have no idea how (eg) Fedora manage FPC but I sure would not use Rawhide !

Davo

[JuhaManninen]

My guess is that Debian, in particular, Abou, has patched it. They don't take ~fixes but do patch particular problems. The FPC in bookworm is at patch level 20 (Bookworm-backports is at 32, but my report above is NOT using backports).

Interesting. It means @calebs used the FPC packages from SourceForge instead of the packages provided by Debian.
I wonder why the latest MX Linux does not use the fixed FPC from Debian. MX Linux is based on Debian after all.

Thus my suggestion that anyone using a Debian based distro probably should just use the disto FPC but build Lazarus from source.

Yes, and that is the best general advice for anybody who is mainly interested in new development and features in Lazarus. Building it from sources is easy.
Building FPC from sources is a little more challenging and then FpcUpDeluxe is a good choice.

[dbannon]

Interesting. It means @calebs used the FPC packages from SourceForge instead of the packages provided by Debian.
I wonder why the latest MX Linux does not use the fixed FPC from Debian. MX Linux is based on Debian after all.

Perhaps MX does not take the updates that Debian generate ?  If they are using a snapshot from earlier 2023, then it may have been before Debian fixed this problem. My MXlinux VM will not boot  :-(  so I will have to build a new one to see what patch level they are on. Don't have time right now. But as I said, Bookworm is on patch 20, bet MXLinux is using something before that.

Its a bit sad that the FPC team have not pushed out an update, maybe we should take the Debian SRC, build a binary and distribute that ?   ;-)

Davo

[dbannon]

.....
I wonder why the latest MX Linux does not use the fixed FPC from Debian. MX Linux is based on Debian after all.

OK, something funny here, wondering the same thing, so, ran up a 32bit MX VM and, to my surprise, it too builds perfectly for me. It does use the exact same FPC package as Debian Bookworm, as we suspected. So, what am I doing differently ?

Attached is the script I use to install FPC (from repo) and Lazarus (from source).

Davo

[JuhaManninen]

OK, something funny here, wondering the same thing, so, ran up a 32bit MX VM and, to my surprise, it too builds perfectly for me. It does use the exact same FPC package as Debian Bookworm, as we suspected. So, what am I doing differently ?

You use the latest MX-23 release I guess.
My information was outdated, from July last year. Then MX-23 was in RC phase. Soon after they released it. Now I can see they released MX-23.2 few days ago.
I will continue my 32-bit e-machines exercise later in a cottage.

[dbannon]

You use the latest MX-23 release I guess.
My information was outdated, from July last year. Then MX-23 was in RC phase. Soon after they released it. Now I can see they released MX-23.2 few days ago.
I will continue my 32-bit e-machines exercise later in a cottage.

Ah, sorry, I did not notice the 32bit image I pulled down was "brand new". So, thats how they work, makes sense. From time to time, grab a snapshot of Debian. Good.

But that still leaves us with a non functional FPC in Source Forge for 32 bit users ?

Davo

[calebs]

hello people i tried this again.
download latest debian 12 iso 32bits. Installed on vm, apt updated all.
installed al prerequisites sugested on fpcupdeluxe page
then downloaded latest fpcupdeluxe 32 bit linux executable (currently 2.4.0c).
checked gitlab check, selefcted fpc 3.2.2 and stable lazarus
clicked on "install/update fpc+lazarus" button, process started and then this error again

Code: Pascal  [Select][+][-]

1. Linking fpmake
2. /bin/ld: /home/usuario/fpcupdeluxe/322stable/fpcsrc/rtl/units/i386-linux/si_c21.o: en la función `SI_C21_$$__FPC_LIBC21_START':
3. si_c21.pp:(.text.n_si_c21_$$__fpc_libc21_start+0x27): referencia a `__libc_csu_fini' sin definir
4. /bin/ld: si_c21.pp:(.text.n_si_c21_$$__fpc_libc21_start+0x2c): referencia a `__libc_csu_init' sin definir
5. make[1]: *** [Makefile:2682: packages_smart] Error 2
6. make: *** [Makefile:2837: build-stamp.i386-linux] Error 2
7. fpmake.pp(58,1) Error: Error while linking
8. fpmake.pp(58,1) Fatal: There were 1 errors compiling module, stopping
9. Fatal: Compilation aborted
10. make[2]: se sale del directorio '/home/usuario/fpcupdeluxe/322stable/fpcsrc/packages'
11. make[1]: se sale del directorio '/home/usuario/fpcupdeluxe/322stable/fpcsrc'
12. make: se sale del directorio '/home/usuario/fpcupdeluxe/322stable/fpcsrc'
13.  
14. fpcupdeluxe: ERROR: FPC Native Installer (BuildModule: FPC): Error running /usr/bin/make for FPC failed with exit code 512
15. . Details: .
16.  
17.  
18. ERROR: Fpcupdeluxe fatal error !
19. Sequencer (FPC): Failure running fpcupdeluxe: error executing sequence FPC
20. Sequencer (Default): Failure running fpcupdeluxe: error executing sequence Default

i must say that i-ve doing this exactly since 2.x and always worked fine. No need to download fpc or lazarus from website or repositories.
btw, doing this on debian x64 it works as expected and no errors.

[TRon]

i must say that i-ve doing this exactly since 2.x and always worked fine. No need to download fpc or lazarus from website or repositories.
btw, doing this on debian x64 it works as expected and no errors.

As already stated it was reported (and addressed).

Finally I was able to locate the corresponding commits (always nice when the issue (link) is mentioned in the commit message  )
- 46a316791c53e9db4a54d86583961b619dbfe041
- b12bb768ca96562a2021d94a7be5857b0c5b2591
- 26fb75ed777bde4397554ecfaf414099e68bceb9
- 4480f65e98b79c15a506b14e8f7ca084f16afbc6
- c949b97c42c7630d3288af932d9effd4321cb756

Thus, you can try and keep compiling 3.2.2 all that you want but that is not going to solve the error. The thing I do not know for sure is if these commits made it into 3.2 fixes (yet). sorry as JuhaManninen already answered that for us (the answer is yes).

[JuhaManninen]

then downloaded latest fpcupdeluxe 32 bit linux executable (currently 2.4.0c).
checked gitlab check, selefcted fpc 3.2.2 and stable lazarus
clicked on "install/update fpc+lazarus" button, process started and then this error again

Please read what dbannon and myself wrote earlier here.
Now you repeated the same failing process again and then you expect a different result.
Dump fpcupdeluxe, you don't need it for this task.

The thing I do not know for sure is if these commits made it into 3.2 fixes (yet).

Yes they made it. FPC's slow release cycle is truly annoying. I don't know how to put it nicely.

[TRon]

@JuhaManninen:
Yes, terribly sorry about that. I only skimmed trough the thread and did not register that you mentioned it.

The release cycle is indeed a tad slow which can indeed be a bit of an annoyance when you are depending on some of these fixes. I'm sure the people behind the scenes do their best, after all it isn't exactly a payed job 

[JuhaManninen]

Yes but still ...
FPC 3.2.2 was released in May 2021.
 https://forum.lazarus.freepascal.org/index.php/topic,54712.0.html
That is soon 3 years ago!
Let's see if we get a new bug fix "dot" release 3.2.4 before the 3. birthday.
I understand if a major release takes 3 years to make, but minor bug fix releases should come out in few months intervals.