Re: glibc 2.27: 3 weeks till release

[Florian Weimer <fweimer at redhat dot com>]

On 01/17/2018 11:36 PM, Carlos O'Donell wrote:
> On 01/11/2018 11:46 PM, Florian Weimer wrote:
> > On 01/12/2018 05:15 AM, Carlos O'Donell wrote:
> > > On 01/11/2018 08:03 AM, Rafal Luzynski wrote:
> > > > Shouldn't we consider my patches for alternative month names as
> > > > ABI change as well? Just to reiterate:
> > > >
> > > > * nl_langinfo() family: + the meaning of MON_x and ABMON_x
> > > > constants has been changed,
> >
> > > This is a API change, but not an ABI change.
> >
> > What's the impact on statically linked applications?  Will they
> > continue to be able to read both kinds of locale data?
>
> Officially speaking, statically linked applications which are not
> recompiled to the new runtime are unsupported, everything else is
> just an extension of the inevitable day when your static binary
> fails to work with the installed data. The key is to provide a
> fallback, in this case your setlocale() call would fail and you'd
> get only C/POSIX builtins.

But this might have to change.  Static linking (with PIE) appears to be 
one of the more attractive ways to reduce indirect branches.

Is there an easy way to change the locale data encoding so that 
statically linked binaries will simply ignore the extra bits introduced 
by the ALTMON change?

Thanks,
Florian