From: Paul Eggert <eggert@cs.ucla.edu>
To: Wookey <wookey@wookware.org>
Cc: Bruno Haible <bruno@clisp.org>, Zack Weinberg <zack@owlfolio.org>,
Sam James <sam@gentoo.org>, Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>,
autoconf@gnu.org, c-std-porting@lists.linux.dev,
toolchain@gentoo.org, bug-gnulib@gnu.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: On time64 and Large File Support
Date: Sat, 12 Nov 2022 13:31:04 -0800 [thread overview]
Message-ID: <b4d95da1-944e-3f54-0d95-0d8162e09a97@cs.ucla.edu> (raw)
In-Reply-To: <20221112202321.GO27919@mail.wookware.org>
On 2022-11-12 12:23, Wookey wrote:
> we can't just have everyone who enabled LFS sometime in the
> last 20 years suddenly being forced into the time_t change (can we?)
We've done it in the past.
AC_SYS_LARGEFILE originally was in Gnulib, before it migrated to
Autoconf. Originally it affected only off_t; its effect on other types
like ino_t came later. Hence people who initially used AC_SYS_LARGEFILE
were later "suddenly forced" into an ino_t width change. Similarly for
other non-off_t types that AC_SYS_LARGEFILE affects.
So there's longstanding precedent for AC_SYS_LARGEFILE changing the
width of system types that were formerly unaffected. The difference is
that time_t is more widely used than ino_t etc., and people are
understandably more concerned about time_t changes.
Because of the concerns raised in this thread it's become clear that
what's in Autoconf now is too drastic, and I've proposed (though not yet
implemented) a change that will cause AC_SYS_LARGEFILE to continue to
not affect time_t unless there's an affirmative request like
"./configure --enable-year2038". I am waiting for feedback on that from
Zack and others, and am hoping for quick turnaround on this because we
do need a new Autoconf release.
next prev parent reply other threads:[~2022-11-12 21:31 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:38 Sam James
2022-11-11 9:16 ` Paul Eggert
2022-11-11 9:19 ` Sam James
2022-11-11 23:48 ` Joseph Myers
2022-11-11 9:19 ` Florian Weimer
2022-11-11 9:27 ` Sam James
2022-11-11 11:38 ` Florian Weimer
2022-11-11 20:12 ` Paul Eggert
2022-11-12 2:20 ` Zack Weinberg
2022-11-12 3:57 ` Sam James
2022-11-12 14:16 ` Zack Weinberg
2022-11-12 17:41 ` Paul Eggert
2022-11-12 18:50 ` Bruno Haible
2022-11-12 19:15 ` Paul Eggert
2022-11-12 20:23 ` Wookey
2022-11-12 20:54 ` Russ Allbery
2022-11-12 21:31 ` Paul Eggert [this message]
2022-11-15 5:09 ` Sam James
2022-11-12 18:19 ` Paul Eggert
2022-11-11 9:40 ` Andreas K. Huettel
2022-11-11 11:30 ` Florian Weimer
2022-11-11 19:01 ` Andreas K. Huettel
2022-11-11 19:28 ` Palmer Dabbelt
2022-11-11 9:46 ` Paul Eggert
2022-11-11 11:22 ` Florian Weimer
2022-11-11 19:56 ` Paul Eggert
2022-11-12 4:20 ` Wookey
2022-11-12 4:28 ` Sam James
2022-11-12 4:56 ` Wookey
2022-11-12 4:59 ` Sam James
2022-11-12 18:33 ` Paul Eggert
2022-11-14 8:39 ` Adam Sampson
2022-11-14 11:47 ` Florian Weimer
2022-11-14 20:26 ` Arsen Arsenović
2022-11-14 20:52 ` Florian Weimer
2022-11-15 7:39 ` Arsen Arsenović
2022-11-11 10:25 ` Richard Purdie
2023-03-01 22:38 ` Eric Blake
2023-03-02 0:29 ` Demi Marie Obenour
2023-03-02 9:04 ` Daniel P. Berrangé
2023-03-02 10:28 ` Paul Eggert
2023-03-02 10:38 ` Andreas Schwab
2023-03-03 5:46 ` Paul Eggert
2023-03-06 8:58 ` Andreas Schwab
2023-03-06 10:19 ` Florian Weimer
2023-03-02 11:02 ` Richard W.M. Jones
2023-03-02 12:17 ` Bruno Haible
2023-03-02 13:24 ` Daniel P. Berrangé
2023-03-03 3:30 ` Wookey
2023-03-03 5:50 ` Paul Eggert
2023-03-03 14:01 ` Wookey
2023-03-03 14:14 ` Daniel P. Berrangé
2023-03-03 23:21 ` Arsen Arsenović
2023-03-03 11:49 ` Florian Weimer
2023-03-03 12:39 ` Richard W.M. Jones
2023-03-02 8:30 ` Richard W.M. Jones
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=b4d95da1-944e-3f54-0d95-0d8162e09a97@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=arnd@arndb.de \
--cc=autoconf@gnu.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=c-std-porting@lists.linux.dev \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=sam@gentoo.org \
--cc=toolchain@gentoo.org \
--cc=wookey@wookware.org \
--cc=zack@owlfolio.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).