From: Sam James <sam@gentoo.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries
Date: Wed, 1 Feb 2023 19:54:31 +0000 [thread overview]
Message-ID: <7E7D8ACE-4095-4A91-AAD7-807D7CBB221D@gentoo.org> (raw)
In-Reply-To: <119ADDA5-39E5-40EF-84CB-6524E20D8D36@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
> On 1 Feb 2023, at 19:47, Sam James via Libc-alpha <libc-alpha@sourceware.org> wrote:
> [snip]
>
> Then we're back to:
> 1. How do we stop people doing it dangerously?
> 2. How do we enable distributions interested in supporting
> cases where the hardware only works for 32-bit & they can
> rebuild their userland in its entirety?
>
> If we don't want to do 2. yet, then we need to figure out
> something for 1. Saying "wait because there aren't
> the resources to make the migration sane yet" would
> work.
One more thing: I'm fine with us saying to wait, because
ideally we'd be done (lol) with Modern C porting first,
because implicit function declarations affect doing mass-
rebuilds anyway if someone is doing this via the package
manager rather than hard-changing the glibc default.
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2023-02-01 19:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 23:57 The time64 and Large File Support mess Andreas K. Huettel
2023-01-25 23:58 ` time64 / Large File Support: 1) [2.28 Regression]: New getdents{64} implementation breaks qemu-user Andreas K. Huettel
2023-01-26 12:21 ` Adhemerval Zanella Netto
2023-01-27 20:08 ` Andreas K. Huettel
2023-01-25 23:59 ` time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries Andreas K. Huettel
2023-01-26 4:13 ` Paul Eggert
2023-01-26 13:21 ` Adhemerval Zanella Netto
2023-01-26 23:35 ` Sam James
2023-01-27 17:33 ` Adhemerval Zanella Netto
2023-02-01 16:26 ` Florian Weimer
2023-02-01 19:47 ` Sam James
2023-02-01 19:54 ` Sam James [this message]
2023-02-03 17:52 ` Florian Weimer
2023-02-01 22:22 ` Michael Hudson-Doyle
2023-02-03 14:17 ` Adhemerval Zanella Netto
2023-02-03 18:56 ` Florian Weimer
2023-01-27 2:38 ` Paul Eggert
2023-01-27 17:40 ` Adhemerval Zanella Netto
2023-01-27 23:51 ` Paul Eggert
2023-01-27 23:58 ` Joseph Myers
2023-02-01 12:27 ` Adhemerval Zanella Netto
2023-01-26 10:43 ` Florian Weimer
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=7E7D8ACE-4095-4A91-AAD7-807D7CBB221D@gentoo.org \
--to=sam@gentoo.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--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).