FPC 3.2.4-rc1 available

[Espectr0]

I replace this version with Lazarus 4 version 3.2.2 and that's it?

[Thaddy]

No, the register updates for AARCH64 are only in 3.3.1. not in 3.2.4 nor 3.2.2.
It is the compiler, not Lazarus. Lazarus is NOT a compiler. FPC is...

[Espectr0]

I mean, is it enough to replace 3.2.2 with 3.2.4?

[Thaddy]

No. The RC1 3.2.4 does not contain the AARCH64 updates. Just Main/Trunk does: 3.3.1.

[robert rozee]

The main highlights of this version:

• Issues with newer glibc fixed

hi PascalDragon,
    what are the nature of these fixes? do they resolve the symbol versioning issues that block binaries built on newer Linux systems from being run on older systems?


cheers,
rob   :-)

[marcov]

    what are the nature of these fixes? do they resolve the symbol versioning issues that block binaries built on newer Linux systems from being run on older systems?

That would be a quite major change, so unlikely in a fixes point release. So probably no.

And if it is not in trunk, it won't be in a fixes release to begin with. If you have specific revisions in trunk, I can lookup some status.

[PascalDragon]

    what are the nature of these fixes?

Removal of some symbols from newer libc versions.

do they resolve the symbol versioning issues that block binaries built on newer Linux systems from being run on older systems?

No.

[robert rozee]

    what are the nature of these fixes?

Removal of some symbols from newer libc versions.
[...]

are you saying that there are some symbols, present in earlier glibc versions, that are no longer present in current versions of glibc?! from my dealings with the glibc developers a year or two back, i understood that we had a promise that no symbols would ever be removed - thereby guaranteeing a level of version compatibility provided a few simple rules were followed.


cheers,
rob   :-)

[marcov]

are you saying that there are some symbols, present in earlier glibc versions, that are no longer present in current versions of glibc?! from my dealings with the glibc developers a year or two back, i understood that we had a promise that no symbols would ever be removed - thereby guaranteeing a level of version compatibility provided a few simple rules were followed.

Only when linked with the corresponding crt* files. FPC has its own, that sometimes causes problems.

[PascalDragon]

    what are the nature of these fixes?

Removal of some symbols from newer libc versions.
[...]

are you saying that there are some symbols, present in earlier glibc versions, that are no longer present in current versions of glibc?! from my dealings with the glibc developers a year or two back, i understood that we had a promise that no symbols would ever be removed - thereby guaranteeing a level of version compatibility provided a few simple rules were followed.

See here.