| Summary: | eSDK install: gcc-source-14.2.0.do_fetch attempted to execute unexpectedly | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] eSDK | Reporter: | Tony Battersby <tonyb> |
| Component: | eSDK | Assignee: | Sermsity Sunil Kumar Dora <SunilKumar.Dora> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Francisco Pedraza <francisco.j.pedraza.gonzalez> |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | JPEWhacker, maganuru.jayasurya, Maganuru.Jayasurya, randy.macleod, sundeep.kokkonda |
| Version: | 5.1.1 | ||
| Target Milestone: | 5.3 M2 | ||
| Hardware: | x86 | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Tony Battersby
2025-01-24 15:51:23 UTC
Sunil, Have you been able to reproduce this defect? Hi Randy, Yes, I was able to reproduce the defect with the following steps: In meta/recipes-core/images/core-image-base.bb, I added: -- IMAGE_FSTYPES = "tar" In conf/local.conf, I set: -- MACHINE = "genericx86-64" Ran: -- bitbake -c populate_sdk_ext core-image-base Then attempted to install the generated eSDK: -- ./tmp/deploy/sdk/poky-glibc-x86_64-core-image-base-core2-64-genericx86-64-toolchain-ext-5.1.1.sh ================= Outcome: The issue is reproducible on both the Poky master and Walnaskar branches. However, I do not observe this issue on Scarthgap. BitBake expects to reuse prebuilt artifacts but can't find them. I am comparing these components between Scarthgap and master branches. Joshua, This gcc-source-14.2.0.bb:do_fetch failure is related to missing setscene tasks and it arose after switching from SPDX 2.2 to 3.0 https://git.openembedded.org/openembedded-core/commit/meta/classes/create-spdx.bbclass?id=beef4c1a3e9fd8fa9cdbbb61e1bc3931012735b3 One can work-around the problem with: echo 'BB_SETSCENE_ENFORCE = "0"' >> conf/local.conf should Sunil (or Jayasura who will take over the issue soon), try to override this in the gcc-source code or is there a better approach? |