From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ross Burton <ross.burton@arm.com>
Cc: Lukasz Majewski <lukma@denx.de>,
Alexander Kanavin <alex.kanavin@gmail.com>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
Yocto-mailing-list <yocto@lists.yoctoproject.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
Date: Wed, 30 Nov 2022 16:59:28 +0000 [thread overview]
Message-ID: <f63f222e6c7bd50f1b50ffb198c61864a67f9ef2.camel@linuxfoundation.org> (raw)
In-Reply-To: <Y4eLLpnUKLz+YiwM@mail.local>
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...
> >
>
> We can simply disable COMPAT_32BIT_TIME in the kernel config.
That would cause runtime issues but not build time linking ones?
Cheers,
Richard
next prev parent reply other threads:[~2022-11-30 16:59 UTC|newest]
Thread overview: 29+ 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 10:52 ` Stephen John Smoogen
2022-11-30 11:04 ` Lukasz Majewski
2022-11-30 12:09 ` Alexander Kanavin
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 [this message]
2022-12-05 10:00 ` Ola x Nilsson
2022-12-05 11:04 ` Richard Purdie
2022-12-05 11:05 ` Ola x Nilsson
2022-12-01 10:27 ` Alexander Kanavin
2022-12-01 10:36 ` Richard Purdie
2022-11-30 16:38 ` Khem Raj
[not found] ` <52fce46ab9bb0f8e298e9ac92a90fd06d46bd35a.camel@codeconstruct.com.au>
2022-12-05 23:24 ` [OE-core] " 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=f63f222e6c7bd50f1b50ffb198c61864a67f9ef2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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=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