4.0 release and debian bookworm high cpu count build errors

[David Miler]

Good morning,

Debian Bookworm, on which the container is based, comes with libglib2.0-0 (2.74.6-2).

That unfortunately introduces build issues in high cpu count environments(https://github.com/microsoft/vcpkg/issues/24960). Making kas 4.0 release unusable for build servers and high performance workstations. 

We have also encountered errors when using devtool modify where bitbake would fail to parse the recipes due to git command returning 128. But we have not found the cause for that one yet.

Thank you,

David

[Jan Kiszka]

On 11.07.23 01:45, 'David Miler' via kas-devel wrote:
> Good morning,
> Debian Bookworm, on which the container is based, comes
> with libglib2.0-0 (2.74.6-2)

> <https://packages.debian.org/bookworm/libglib2.0-0>.

> That unfortunately introduces build issues in high cpu count
> environments(https://github.com/microsoft/vcpkg/issues/24960). Making
> kas 4.0 release unusable for build servers and high performance
> workstations. 

OK. Is there also a related Debian bug report that tracks this issue,
linking it to the upstream bug?

>
> We have also encountered errors when using devtool modify where bitbake
> would fail to parse the recipes due to git command returning 128. But we
> have not found the cause for that one yet.

Also that is 4.0-only, not happening with 3.3?

Thanks,
Jan

--
Siemens AG, Technology
Competence Center Embedded Linux

[David Miler]

Hello, sorry for the late reply.

This is only happening on 4.0. 3.3 works fine(Except for the pyyaml issue from this morning https://github.com/yaml/pyyaml/issues/601). I had been focusing on other more pressing issue so I don't have much time to debug this issue any further for now. We have locked our builds to kas3.3 and from time to time I will be monitoring if the debian image starts working. I am hoping debian will backport a patch for this at some point. 

Best,

David

[Jan Kiszka]

On 18.07.23 04:16, 'David Miler' via kas-devel wrote:
> Hello, sorry for the late reply.
> This is only happening on 4.0. 3.3 works fine(Except for the pyyaml
> issue from this morning https://github.com/yaml/pyyaml/issues/601). I
> had been focusing on other more pressing issue so I don't have much time
> to debug this issue any further for now. We have locked our builds to
> kas3.3 and from time to time I will be monitoring if the debian image
> starts working. I am hoping debian will backport a patch for this at
> some point. 

Well, if no one reports to Debian, very likely nothing will change. I
can't as I don't have all the required information on how to reproduce.

Jan

>
> Best,
> David
> On Monday, July 10, 2023 at 11:18:51 PM UTC-7 Jan Kiszka wrote:
>
> On 11.07.23 01:45, 'David Miler' via kas-devel wrote:
> > Good morning,
> > Debian Bookworm, on which the container is based, comes
> > with libglib2.0-0 (2.74.6-2)
> > <https://packages.debian.org/bookworm/libglib2.0-0
> <https://packages.debian.org/bookworm/libglib2.0-0>>.
> > That unfortunately introduces build issues in high cpu count
> > environments(https://github.com/microsoft/vcpkg/issues/24960

> <https://github.com/microsoft/vcpkg/issues/24960>). Making