On Sat, Aug 26, 2023 at 10:08 PM Weihmann, Konrad (Avnet Embedded)
<konrad.weihm...@avnet.eu> wrote:
>
> Hi all,
>
>
>
> this mentioned patch is needed to fix the currently broken Yocto 4.0.12 
> release.
>
> This there a plan to issue a hotfix tag release, or will this be part of the 
> next 4.0.13 in roughly 6 weeks?

The above referenced patch is in my current test queue. If all goes
well in testing it should be pushed to the poky kirkstone branch
mid-week.

> I’m also wondering how the original patch could have not failed at least two 
> times on the auto-builder (patch and release level).
> That might need to be investigated.

The fix patch mentions that the issue leads to "undefined symbol error
on certain architectures", but doesn't identify which architectures
specifically.

Siddarth, Archana: Do you know which architectures display the issue?

Once we know this, I can comment on why local and autobuilder testing
didn't catch this.  At this point all I can say is that none of the
architectures tested on my local machine or the autobuilder displayed
this issue.

Steve

> Regards
>
> Konrad
>
>
>
> We continuously commit to comply with the applicable data protection laws and 
> ensure fair and transparent processing of your personal data.
> Please read our privacy statement including an information notice and data 
> protection policy for detailed information on our website.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186773): 
https://lists.openembedded.org/g/openembedded-core/message/186773
Mute This Topic: https://lists.openembedded.org/mt/100951881/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to