From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: "yann.morin.1998@free.fr" <yann.morin.1998@free.fr>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] Config.in: introduce BR2_TIME_BITS_64 option for Y2038 compatibility
Date: Thu, 13 Oct 2022 16:39:10 +0200 [thread overview]
Message-ID: <20221013163910.3c6d9c8f@windsurf> (raw)
In-Reply-To: <5eebf7dee2a585f50a4e986c214677a157bfd22c.camel@calian.com>
On Wed, 12 Oct 2022 23:49:37 +0000
Robert Hancock <robert.hancock@calian.com> wrote:
> There's some chance of software being broken by enabling this, with
> either a compile or runtime failure. For example, applications that
> assume sizeof(time_t) == sizeof(long) would work on 32-bit platforms
> with a 32-bit time and 64-bit platforms with a 64-bit time, but fail
> with a 64-bit time on 32-bit. I believe I've seen this when trying to
> build software with that option, so turning this on unconditionally
> might be unwise, unless some build tests of the supported packages
> have been done..
There will definitely be build testing: our autobuilders are testing
24/7 random configurations of Buildroot. So as soon as we introduce
this option, there would be builds with BR2_TIME_BITS_64=y enabled,
which would raise build issues if there's any.
Of course, the more tricky part are runtime issues, which are
essentially impossible to detect until someone runs into the problem.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-13 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 21:50 [Buildroot] [PATCH] Config.in: introduce BR2_TIME_BITS_64 option for Y2038 compatibility Thomas Petazzoni via buildroot
2022-10-12 23:49 ` Robert Hancock via buildroot
2022-10-13 14:39 ` Thomas Petazzoni via buildroot [this message]
2023-02-06 20:25 ` Romain Naour
2023-02-06 22:06 ` Romain Naour
2022-10-13 8:27 ` Peter Korsgaard
2023-10-01 19:15 ` Thomas Petazzoni via buildroot
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=20221013163910.3c6d9c8f@windsurf \
--to=buildroot@buildroot.org \
--cc=robert.hancock@calian.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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