From: Alain GUILLEMOT <alain.guillemot@asn.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Florian Weimer <fweimer@redhat.com>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: RE: Glibc on target 32 bits with 64-bit time support
Date: Thu, 18 May 2023 19:49:39 +0000 [thread overview]
Message-ID: <PAZP264MB441437CF41C85330118F9B38E47F9@PAZP264MB4414.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230518124656.28b97ae1@wsk>
Thank's for the answer, I will test it next week.
A+
-----Message d'origine-----
De : Lukasz Majewski <lukma@denx.de>
Envoyé : jeudi 18 mai 2023 12:47
À : Alain GUILLEMOT <alain.guillemot@asn.com>
Cc : Florian Weimer <fweimer@redhat.com>; libc-help@sourceware.org
Objet : Re: Glibc on target 32 bits with 64-bit time support
Hi Alain,
> Hi Florian
>
> OK, that means that since glibc 2.34, glibc automatically recognizes
> whether the time_t structure is 32 or 64 bits.
>
> And therefore only the applications must be recompiled with the flags
> "-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64" ).
>
>
> This is correct ?
In principle yes.
Please find some extra information regarding glibc integration with 64 bit time support.
https://urldefense.com/v3/__https://github.com/lmajewski/meta-y2038*readme__;Iw!!HqwE!OnXimeUXo9KINuxtprxS7lYTXshhXz0xlRq3nBN_xR8FktKu9dTiEthPRSULKfz-5PbSfmtj0NvSWjUN$
>
>
> De : Florian Weimer <fweimer@redhat.com> Envoyé : lundi 15 mai 2023
> 22:12 À : Alain GUILLEMOT <alain.guillemot@asn.com> Cc :
> libc-help@sourceware.org Objet : Re: Glibc on target 32 bits with
> 64-bit time support
>
> * Alain GUILLEMOT: > In which file I have to add the option
> "-D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64", or are these options to be
> passed on the command > line? All ABI variants are automatically
> built. You don't have to do anything
>
>
> * Alain GUILLEMOT:
>
>
>
> > In which file I have to add the option "-D_FILE_OFFSET_BITS=64
>
> > -D_TIME_BITS=64", or are these options to be passed on the command
>
> > line?
>
>
>
> All ABI variants are automatically built. You don't have to do
> anything
>
> while building glibc. These flags are for building applications with
>
> glibc.
>
>
>
> Thanks,
>
> Florian
>
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
prev parent reply other threads:[~2023-05-18 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 18:25 Alain GUILLEMOT
2023-05-15 20:11 ` Florian Weimer
2023-05-16 17:20 ` Alain GUILLEMOT
2023-05-16 17:53 ` Florian Weimer
2023-05-18 10:31 ` Alain GUILLEMOT
2023-05-18 10:46 ` Lukasz Majewski
2023-05-18 19:49 ` Alain GUILLEMOT [this message]
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=PAZP264MB441437CF41C85330118F9B38E47F9@PAZP264MB4414.FRAP264.PROD.OUTLOOK.COM \
--to=alain.guillemot@asn.com \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=lukma@denx.de \
/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).