From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH RFC 3/3] time64.conf: Include to enable 64 bit time flags
Date: Fri, 9 Dec 2022 11:31:48 +0100 [thread overview]
Message-ID: <jwq1qp8dfud.fsf@axis.com> (raw)
In-Reply-To: <029656ba7b1a8f22d017aa317abba98390ec1507.camel@linuxfoundation.org>
On Thu, Dec 08 2022, Richard Purdie wrote:
> On Thu, 2022-12-08 at 11:00 +0100, Alexander Kanavin wrote:
>> On Thu, 8 Dec 2022 at 08:11, Ola x Nilsson <olani@axis.com> wrote:
>> > +# TODO: Only for 32-bit architectures?
>> > +TARGET_CC_ARCH:append:arm = " ${GLIBC_64BIT_TIME_FLAGS}"
>> > +TARGET_CC_ARCH:append:armeb = " ${GLIBC_64BIT_TIME_FLAGS}"
>> > +TARGET_CC_ARCH:append:mips32el = " ${GLIBC_64BIT_TIME_FLAGS}"
>>
>> On the contrary, why not set this globally?
>
> The 64 bit architectures don't need this and should "just work" so it
> is probably better just to set this where needed. At the very least
> that will keep the compiler command lines a bit cleaner.
It also changes the hashes for no good reason, right?
Khem suggested using SITEINFO_BITS, I'll see if that works.
--
Ola x Nilsson
next prev parent reply other threads:[~2022-12-09 10:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 7:11 Y2038: Sanity checker for non-64-bit time and file functions Ola x Nilsson
2022-12-08 7:11 ` [PATCH RFC 1/3] glibc: Add ppoll fortify symbol for 64 bit time_t Ola x Nilsson
2022-12-08 7:11 ` [PATCH RFC 2/3] Add QA check for 32 bit time and file offset functions Ola x Nilsson
2022-12-17 11:17 ` [OE-core] " Richard Purdie
2022-12-17 17:19 ` Khem Raj
2022-12-08 7:11 ` [PATCH RFC 3/3] time64.conf: Include to enable 64 bit time flags Ola x Nilsson
2022-12-08 10:00 ` [OE-core] " Alexander Kanavin
2022-12-08 10:10 ` Richard Purdie
2022-12-09 10:31 ` Ola x Nilsson [this message]
2022-12-09 10:36 ` Ola x Nilsson
2022-12-09 13:06 ` Alexandre Belloni
2022-12-09 0:23 ` Khem Raj
2022-12-09 9:55 ` Ola x Nilsson
2022-12-09 12:35 ` Richard Purdie
2022-12-09 13:09 ` Alexandre Belloni
2022-12-09 13:13 ` Alexander Kanavin
2022-12-09 13:29 ` Richard Purdie
2022-12-09 16:36 ` Khem Raj
2022-12-09 16:47 ` Khem Raj
2022-12-15 16:32 ` Khem Raj
2022-12-17 11:15 ` Richard Purdie
2022-12-16 18:44 ` Khem Raj
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=jwq1qp8dfud.fsf@axis.com \
--to=ola.x.nilsson@axis.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.