Re: [PATCH] Revert "Detect ld.so and libc.so version inconsistency during startup"

[Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>]

On 25/08/22 11:17, Florian Weimer wrote:
> * Adhemerval Zanella Netto:
> 
>> On 25/08/22 03:03, Florian Weimer via Libc-alpha wrote:
>>> This reverts commit 6f85dbf102ad7982409ba0fe96886caeb6389fef.
>>>
>>> Once this change hits the release branches, it will require relinking
>>> of all statically linked applications before static dlopen works
>>> again, for the majority of updates on release branches: The NEWS file
>>> is regularly updated with bug references, so the __libc_early_init
>>> suffix changes, and static dlopen cannot find the function anymore.
>>>
>>> While this ABI check is still technically correct (we do require
>>> rebuilding & relinking after glibc updates to keep static dlopen
>>> working), it is too drastic for stable release branches.
>>
>> Sounds reasonable, although this is a configure options not enabled by
>> default.  Maybe extend the notes on either documentation and release wiki
>> to describe the pitfalls of this option?
> 
> The hash suffix is always active, even without the configure option.  So
> no, we can't leave this in as an optional feature.
> 

Can't we make it optional then iff the configure option is enable to a
version different than an empty one? Basically making the default as is
and if user adds --with-extra-version-id= to use the new scheme? 

I will change the GLIBC_PRIVATE abi, but I think it should be expected.