Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

I sent patches to fix the ninja issue. These were needed for kirkstone and scarthgap. styhead was fine On Sat, Nov 23 2024 at 01:17:35 PM +01:00:00, Markus Volk wrote: I managed to work around the ninja-native problem by simply calling 'bitbake -c do_configure gcc', which works, and then bitb

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

I managed to work around the ninja-native problem by simply calling 'bitbake -c do_configure gcc', which works, and then bitbake gcc Like this ninja-native also fails, but gcc is built. So I can at least confirm that the patch is applied and gcc compiles on scarthgap. For kirkstone this patch d

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

It's not that I didnt't try, but it seams like I cant build gcc for scarthgap from my host system (which is based on master branch) I'm lacking pipes due to python 3.13 ERROR: ninja-native-1.11.1-r0 do_compile: ExecutionError('/home/flk/poky/build-test/tmp/work/x86_64-linux/ninja-native/1.11.1/

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

On Fri, Nov 22 2024 at 05:33:29 AM -08:00:00, Steve Sakoman wrote: Markus, could you send versions of this patch for stable branches too? (styhead, scarthgap, kirkstone) I have sent the patches, but only verified that they would apply. I can't comile test them as I dont have buildsystems set

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

On Thu, Nov 21, 2024 at 5:35 PM Martin Jansa wrote: > > Should the backport of tzdata update like > https://lists.openembedded.org/g/openembedded-core/message/207561 > for scarthgap and > https://lists.openembedded.org/g/openembedded-core/message/207428 > for styhead be delayed a bit so that this

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

On Thu, Nov 21 2024 at 07:04:06 PM -08:00:00, Khem Raj wrote: Patch is fine however I would suggest to remove the hunk changing changellog files it will make it easy to backport Removed the comments on the changelog from the commit message. but I didn't find a hunk that patches Changelog -

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

Patch is fine however I would suggest to remove the hunk changing changellog files it will make it easy to backport On Thu, Nov 21, 2024 at 5:30 PM Markus Volk via lists.openembedded.org wrote: > There is an issue in the std::chrono::tzdb parser that causes problems > since the tzdata-2024b rele

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

On Fri, Nov 22 2024 at 02:35:37 AM +01:00:00, Martin Jansa wrote: I don't know how widespread this is (or what is waybar clock module) The issue was discussed here -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. V

Re: [oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

Should the backport of tzdata update like https://lists.openembedded.org/g/openembedded-core/message/207561 for scarthgap and https://lists.openembedded.org/g/openembedded-core/message/207428 for styhead be delayed a bit so that this gcc change can go at the same time? I don't know how widespread

[oe-core][PATCH] gcc: add a backport patch to fix an issue with tzdata 2024b

There is an issue in the std::chrono::tzdb parser that causes problems since the tzdata-2024b release started using %z in the main format. As a real world problem I encounter an issue with the waybar clock module, which ignores the timezone setting and only shows system time. Signed-off-by: Marku