From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ross Burton <ross.burton@arm.com>,
Lukasz Majewski <lukma@denx.de>,
Alexander Kanavin <alex.kanavin@gmail.com>,
Yocto-mailing-list <yocto@lists.yoctoproject.org>,
OE-core <openembedded-core@lists.openembedded.org>,
"openembedded-architecture@lists.openembedded.org"
<openembedded-architecture@lists.openembedded.org>
Subject: Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
Date: Mon, 5 Dec 2022 12:05:24 +0100 [thread overview]
Message-ID: <jwq8rjm1564.fsf@axis.com> (raw)
In-Reply-To: <a02da780e14fd8353c2b9d4dedabbf2dbcf971b6.camel@linuxfoundation.org>
On Mon, Dec 05 2022, Richard Purdie wrote:
> On Mon, 2022-12-05 at 11:00 +0100, Ola x Nilsson wrote:
>> On Wed, Nov 30 2022, Richard Purdie wrote:
>>
>> > On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
>> > > On 30/11/2022 16:46:17+0000, Ross Burton wrote:
>> > > > On 30 Nov 2022, at 14:20, Richard Purdie via
>> > > > lists.yoctoproject.org
>> > > > <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
>> > > > > > > * Could we optionally disable some of the glibc 32 bit function calls
>> > > > > > > to ensure they're not being used?
>> > > > > >
>> > > > > > Could you be more specific here? Would you like to disable some
>> > > > > > syscalls?
>> > > > >
>> > > > > I'm meaning disabling the 32 bit glibc time functions.
>> > > >
>> > > > Some time ago I filed
>> > > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian
>> > > > has a nice sanity check where it warns if non-LFS glibc functions
>> > > > are used. I imagine the same logic could be used to check for 32-
>> > > > bit time_t use.
>> >
>> > That sounds interesting and something we should probably look into for
>> > both issues...
>>
>> I have a working sanity checker that checks for any glibc functions
>> affected by -D_FILE_OFFSET_BITS=64 or -D_TIME_BITS=64.
>> The INSANE_SKIP functionality needs some more polish but I'd be happy to
>> contribute it.
>>
>> Some libraries use both 32 and 64 bit APIs to glibc and needs exceptions
>> in the checker.
>>
>> I have not run any world builds with this checker, I've focused on the
>> recipes we actually use so far so we could get to a testable system. My
>> biggest worry at the moment is rust, I know to little to know if it is
>> an actual problem and how to fix it.
>>
>> I would like to be part of any "y2038 team" for Yocto.
>
> That does sound useful, perhaps sharing it as an RFC patch might be a
> good place to start? We might be able to run one of the autobuilder
> world targets against it, see how it looks for our core recipes?
That works for me. I've started preparing a patch for oe-core.
--
Ola x Nilsson
next prev parent reply other threads:[~2022-12-05 11:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 15:44 Yocto Project Status 29 November 2022 (WW48) sjolley.yp.pm
2022-11-30 8:07 ` Y2038 proposal Alexander Kanavin
2022-11-30 8:28 ` [yocto] " Lukasz Majewski
2022-11-30 9:07 ` Alexander Kanavin
2022-11-30 9:40 ` Lukasz Majewski
2022-11-30 9:48 ` Alexander Kanavin
2022-11-30 21:14 ` Alexander Kanavin
2022-12-01 8:28 ` Lukasz Majewski
2022-11-30 11:02 ` Alexandre Belloni
2022-11-30 11:40 ` [OE-core] " Richard Purdie
2022-11-30 12:07 ` Alexander Kanavin
2022-11-30 12:09 ` Lukasz Majewski
2022-11-30 12:11 ` Richard Purdie
2022-11-30 13:15 ` [Openembedded-architecture] " Richard Purdie
2022-11-30 13:36 ` [OE-core] " Lukasz Majewski
2022-11-30 14:20 ` Richard Purdie
2022-11-30 16:46 ` [yocto] " Ross Burton
2022-11-30 16:56 ` Alexandre Belloni
2022-11-30 16:59 ` Richard Purdie
2022-12-05 10:00 ` Ola x Nilsson
2022-12-05 11:04 ` Richard Purdie
2022-12-05 11:05 ` Ola x Nilsson [this message]
2022-12-01 10:27 ` Alexander Kanavin
2022-12-01 10:36 ` Richard Purdie
2022-11-30 16:38 ` Khem Raj
2022-12-02 8:54 ` [OE-core] " Matt Johnston
2022-12-05 23:24 ` Richard Purdie
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=jwq8rjm1564.fsf@axis.com \
--to=ola.x.nilsson@axis.com \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=lukma@denx.de \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--cc=yocto@lists.yoctoproject.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