From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: Florian Weimer <fweimer@redhat.com>, bug-gnulib@gnu.org
Subject: Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64
Date: Fri, 2 Jul 2021 19:40:46 -0700 [thread overview]
Message-ID: <d5d10466-fb0d-8b77-c750-28f02ea09eb2@cs.ucla.edu> (raw)
In-Reply-To: <4302797.ikRTjI96fm@omega>
On 7/2/21 3:29 PM, Bruno Haible wrote:
> the package-by-package approach led to major trouble, and that the
> global approach — use -D_FILE_OFFSET_BITS=64 in all compilations —
> was ultimately the simplest way forward.
Yes, that's pretty much my thought as well.
Like Bruno, I didn't understand Florian's comments. Any apps and/or
libraries compiled with _TIME_BITS=64 will have the API issues Bruno
mentioned, even if the apps and/or libraries don't use Gnulib. I don't
see why these issues would cause distros to abandon 32-bit i386 simply
because of Gnulib.
next prev parent reply other threads:[~2021-07-03 2:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 2:33 [PATCH] year2038: support glibc 2.34 _TIME_BITS=64 Paul Eggert
2021-07-02 15:32 ` Florian Weimer
2021-07-02 22:29 ` Bruno Haible
2021-07-03 2:40 ` Paul Eggert [this message]
2021-07-05 14:32 ` Florian Weimer
2021-07-05 20:14 ` Paul Eggert
2021-07-06 1:34 ` Bruno Haible
2021-07-06 22:29 ` Paul Eggert
2021-07-06 2:11 ` Bruno Haible
2021-07-07 8:45 ` Florian Weimer
2021-07-07 21:58 ` Paul Eggert
2021-07-08 5:36 ` Florian Weimer
2021-07-17 3:39 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5d10466-fb0d-8b77-c750-28f02ea09eb2@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=fweimer@redhat.com \
/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).