diff options
| author | Joao Marcos Costa <joaomarcos.costa@bootlin.com> | 2023-12-27 17:28:24 +0100 |
|---|---|---|
| committer | Joao Marcos Costa <joaomarcos.costa@bootlin.com> | 2023-12-29 14:50:18 +0100 |
| commit | 6579ce9b77f0036454478b2e07694f7314f97867 (patch) | |
| tree | cbb0a5aab6bcca73a65a47bcca7231cfe3bfea33 /classes/use-imx-security-controller-firmware.bbclass | |
| parent | 65ec98511e52f60ddf868a206536893dbe5f2839 (diff) | |
| download | meta-freescale-6579ce9b77f0036454478b2e07694f7314f97867.tar.gz | |
fsl-dynamic-packagearch: fix MACHINE_SOCARCH definition
The sstate manifest for populate_sysroot was not being named
properly for firmware-sentinel and imx-boot-firmware-files, raising the
following error:
The sstate manifest for task 'firmware-sentinel:populate_sysroot'
(multilib variant '') could not be found.
The pkgarchs considered were: microej_imx93, armv7ahf-neon-vfpv4-mx93,
armv7ahf-neon-mx93, (and so on...)
But none of these manifests exists:
...build/tmp-glibc/sstate-control/manifest-microej_imx93-imx-boot-firmware-files.populate_sysroot
...build/tmp-glibc/sstate-control/manifest-armv7ahf-neon-vfpv4-mx93-imx-boot-firmware-files.populate_sysroot
... and so on.
All the other packages were suffixed with TUNE_PKGARCH only, so I couldn't
see the reason why only some specific packages from meta-freescale were using
that.
Remove MACHINE_SOCARCH_SUFFIX so as the sstate manifest is compatible
with what's expected in populate_sysroot.
Signed-off-by: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
Diffstat (limited to 'classes/use-imx-security-controller-firmware.bbclass')
0 files changed, 0 insertions, 0 deletions