From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Wookey <wookey@wookware.org>
Cc: "Paul Eggert" <eggert@cs.ucla.edu>,
"Bruno Haible" <bruno@clisp.org>,
"Richard W.M. Jones" <rjones@redhat.com>,
"Demi Marie Obenour" <demiobenour@gmail.com>,
"Eric Blake" <eblake@redhat.com>, "Sam James" <sam@gentoo.org>,
"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org>,
autoconf@gnu.org, c-std-porting@lists.linux.dev,
"Zack Weinberg" <zack@owlfolio.org>,
"David Seifert" <soap@gentoo.org>,
"Gentoo Toolchain" <toolchain@gentoo.org>,
"Arsen Arsenović" <arsen@aarsen.me>,
dueno@redhat.com
Subject: Re: On time64 and Large File Support
Date: Fri, 3 Mar 2023 14:14:18 +0000 [thread overview]
Message-ID: <ZAIAugEcITc2wSon@redhat.com> (raw)
In-Reply-To: <20230303140135.GX12440@mail.wookware.org>
On Fri, Mar 03, 2023 at 02:01:35PM +0000, Wookey wrote:
> On 2023-03-02 21:50 -0800, Paul Eggert wrote:
> > On 3/2/23 19:30, Wookey wrote:
>
> > > Gnulib automatically changing the ABI for packages that use it
> > > (and have LFS already enabled) is deeply unhelpful...
>
> > This change to Gnulib was reverted in December[1] and that propagated into
> > bleeding-edge GnuTLS last month[2]. So if I understand things correctly the
> > next GnuTLS release will go back to the old way of doing things,
>
> OK. gnulib doesn't seem to have releases as such (last release v0.1 9
> years ago), and is normally used embedded in the upstream source like
> autotools (right?). What is a good test for whether a package/upstream
> is affected by this 'gnulib might have turned 64-bit time' issue? Is
> there an embedded gnulib version one can check, or does one have to look
> at dates of the m4/year2038.m4 and m4/largefile.m4 files in the source?
Looks like you can probably detect it from the configure --help
output. Based on this commit:
> > [1]: https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=7c7c8a519f3892f6f5b30a1c6b22796ab314a45c
The original problematic impl has this:
- AC_ARG_ENABLE([year2038],
- [ --disable-year2038 omit support for timestamps past the year 2038])
the new code which does not enable 2038 by default has
+[AC_ARG_ENABLE([year2038],
+ m4_provide_if([AC_SYS_YEAR2038],
+ [AS_HELP_STRING([--disable-year2038],
+ [do not support timestamps after 2038])],
+ [AS_HELP_STRING([--enable-year2038],
+ [support timestamps after 2038])]))])
So if
configure --help | grep disable-year2038
says 'omit support for timestamps past the year 2038', the app is
suspect and might face ABI compat issues.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-03 14:14 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
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é [this message]
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=ZAIAugEcITc2wSon@redhat.com \
--to=berrange@redhat.com \
--cc=arsen@aarsen.me \
--cc=autoconf@gnu.org \
--cc=bruno@clisp.org \
--cc=c-std-porting@lists.linux.dev \
--cc=demiobenour@gmail.com \
--cc=dueno@redhat.com \
--cc=eblake@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=rjones@redhat.com \
--cc=sam@gentoo.org \
--cc=soap@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).