[fpc-devel] Build failure in Fedora 35 due to glibc 2.34 code hardening

[Karoly Balogh]

Hi

On Sun, 8 Aug 2021, Florian Klämpfl via fpc-devel wrote:

> > One of the guys responsible for glibc in Fedora gave this explanation:
> >
> >> It's related to startup code hardening in glibc.  In general, it's
> >> not forward-compatible to call internal glibc functions this way.
> >> __libc_csu_init and __libc_csu_fini where never part of any header
> >> file. It's not clear to me why fpc needs to replace the startup code.
> >> They could supply a C main function and call Pascall code from that.
> >> Or compile the main program in such a way that it has a compatible
> >> interface with the C main program.
>
> This is not what we want. We just want to initialize glibc from *our*
> startup code for various reasons.

Could you ellaborate on some of these reasons? I mean for example on
Darwin/macOS/etc, we already just link against the startup code shipped by
the SDK of that OS, AFAIR?

> And if a library is written properly, this must be possible.

We're talking about glibc here... :) But snarky remarks aside, if they're
talking about hardening the code, I doubt they'll budge and just revert it
for FPC or anyone. So going ahead it is going to be an issue.

Charlie