Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Michael Halstead <mhalstead@linuxfoundation.org>
Cc: Khem Raj <raj.khem@gmail.com>,
	Bruce Ashfield <bruce.ashfield@gmail.com>,
	 OE-core <openembedded-core@lists.openembedded.org>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3
Date: Tue, 8 Jun 2021 20:15:27 +0200	[thread overview]
Message-ID: <CANNYZj9wKQv+YMgCN98R1fEiCaruFTiK_MHXt+aNPVLOYBBS2w@mail.gmail.com> (raw)
In-Reply-To: <CADfgfoaUpky3zgsU=q90nQdbuPWa63VxQSKQCc=r1YahwKw5oQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]

I can confirm that the previous kernel behaves correctly:
utimensat_time64(AT_FDCWD,
"../install/usr/local/lib/cmake/assimp-4.1/assimp-config.cmake",
[{tv_sec=1623176017, tv_nsec=6290007298941124608}, {tv_sec=1622966579,
tv_nsec=17838646317425885184}], 0) = -1 ENOSYS (Function not implemented)
utimensat(AT_FDCWD,
"../install/usr/local/lib/cmake/assimp-4.1/assimp-config.cmake",
[{tv_sec=1623176017, tv_nsec=0} /* 2021-06-08T18:13:37+0000 */,
{tv_sec=1622966579, tv_nsec=0} /* 2021-06-06T08:02:59+0000 */], 0) = 0

Does look like a botched backport of time64 syscalls to me.

Alex

On Tue, 8 Jun 2021 at 17:40, Michael Halstead <mhalstead@linuxfoundation.org>
wrote:

> I've rebooted centos8-ty-1 using the previous 4.18.0-240.15.1.el8_3.x86_64
> kernel and kept it in the pool. I've paused centos8-ty-2 so it won't
> interfere with builds and left it at the current 4.18.0-305.3.1.el8.x86_64
> kernel for testing.
>
> On Mon, Jun 7, 2021 at 11:04 AM Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
>
>> On Mon, 7 Jun 2021 at 19:18, Khem Raj <raj.khem@gmail.com> wrote:
>>
>>> > I added the needed packages to the CentOS workers. The compiled binary
>>> prints "rc=0" on the three CentOS workers.
>>>
>>> can we now try linking and running it against SDK built nativesdk-glibc ?
>>>
>>
>> Using the host libc won't show the issue, as it is old (2.28), isn't
>> using utimensat_time64 and goes straight to utimensat.
>>
>> With nativesdk-glibc, it still succeeds:
>> utimensat_time64(3, NULL, [{tv_sec=1, tv_nsec=2} /*
>> 1970-01-01T00:00:01.000000002+0000 */, {tv_sec=3, tv_nsec=4} /*
>> 1970-01-01T00:00:03.000000004+0000 */], 0) = 0
>>
>> So we'd need to look into why the kernel accepts this, but rejects the
>> call from cmake. Any easy way to trace this? Just to repeat the failing one:
>>
>> utimensat_time64(AT_FDCWD,
>> "../install/usr/local/lib/cmake/assimp-4.1/assimp-config.cmake",
>> [{tv_sec=1622966723, tv_nsec=6319439026193432576}, {tv_sec=1622966579,
>> tv_nsec=17840053692309438464}], 0) = -1 EINVAL (Invalid argument)
>>
>> Alex
>>
>
>
> --
> Michael Halstead
> Linux Foundation / Yocto Project
> Systems Operations Engineer
>

[-- Attachment #2: Type: text/html, Size: 3317 bytes --]