> The change is supposed to be binary compatible so not sure what this
> means.
Our problem is related with distribution, not with a specific library
or its ABI. Imagine that:
$VENDOR1 builds GNAT without the fix.
$VENDOR2 builds libfoo against GNAT.
$administrator installs both.
I write bar.ad
> Jakub reported that for glibc 2.34 (trunk, unreleased), Richard said it was
> working for glibc 2.33 (latest release), your commit says "Fix build
> breakage with latest glibc release" (which is 2.33). What is correct?
Both I guess, mine is just a bit more forward-looking. ;-)
> The symptom
> "
Jakub reported that for glibc 2.34 (trunk, unreleased), Richard said it was
working for glibc 2.33 (latest release), your commit says "Fix build breakage
with latest glibc release" (which is 2.33). What is correct?
The change also caused CI test failures in Debian and Ubuntu as seen at
https://ci.
This fixes the build breakage introduced by the latest glibc release.
Tested on x86-64/Linux, applied on mainline, 10 and 9 branches.
2021-03-05 Eric Botcazou
PR ada/99264
* init.c (__gnat_alternate_sta) [Linux]: Remove preprocessor test on
MINSIGSTKSZ and bump size t
