From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Rafal Luzynski <digitalfreak@lingonborough.com>,
libc-alpha@sourceware.org, "Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: glibc 2.27: 3 weeks till release
Date: Wed, 17 Jan 2018 22:38:00 -0000 [thread overview]
Message-ID: <b023de44-cd51-2d88-0763-854de85ee8d6@redhat.com> (raw)
In-Reply-To: <e17d9cf7-104c-6331-f17c-7901183ddd48@redhat.com>
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.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-01-17 22:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 3:44 Dmitry V. Levin
2018-01-11 5:10 ` Carlos O'Donell
2018-01-11 13:45 ` Joseph Myers
2018-01-11 14:42 ` Zack Weinberg
2018-01-11 14:46 ` Dmitry V. Levin
2018-01-11 14:51 ` Zack Weinberg
2018-01-11 14:57 ` Dmitry V. Levin
2018-01-11 15:14 ` Zack Weinberg
2018-01-11 16:03 ` Rafal Luzynski
2018-01-12 4:15 ` Carlos O'Donell
2018-01-12 7:47 ` Florian Weimer
2018-01-12 8:10 ` Rafal Luzynski
2018-01-12 17:15 ` Joseph Myers
2018-01-22 23:58 ` Rafal Luzynski
2018-01-23 20:23 ` Carlos O'Donell
2018-01-23 21:57 ` Rafal Luzynski
2018-01-17 22:38 ` Carlos O'Donell [this message]
2018-01-18 11:21 ` Florian Weimer
2018-01-18 11:59 ` Rafal Luzynski
2018-01-18 12:28 ` Florian Weimer
2018-01-18 13:31 ` Joseph Myers
2018-01-18 13:34 ` Florian Weimer
2018-01-12 4:19 ` Carlos O'Donell
2018-01-12 12:54 ` Adhemerval Zanella
2018-01-18 15:30 ` Dmitry V. Levin
2018-01-18 16:42 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b023de44-cd51-2d88-0763-854de85ee8d6@redhat.com \
--to=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=fweimer@redhat.com \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).