diff options
| author | Drew Moseley <drew_moseley@mentor.com> | 2016-02-05 10:56:20 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-02-07 17:30:00 +0000 |
| commit | aacae25a3d7822555343225c7cb06154bd8f4f70 (patch) | |
| tree | 93d5725d3f2d63475bbea853dda653cabe766b34 /meta/classes/package_rpm.bbclass | |
| parent | 9c0d4ece40b9c08416339d3a10cabceb4f5c68c3 (diff) | |
| download | poky-aacae25a3d7822555343225c7cb06154bd8f4f70.tar.gz | |
image_types.bbclass: Embed IMAGE_NAME in ubinize config file
When using the FSTYPE multiubi, make sure that each image build
has a unique config file. Without this there is a race condition
when building multiple images in a single bitbake command which
results in errors similar to:
ERROR: Error: The image creation script
'blah/tmp/work/blah/core-image-base/1.0-r0/temp/create_image.multiubi' returned 1:
iniparser: cannot open ubinize_normal.cfg
ubinize: error!: cannot load the input ini file "ubinize_normal.cfg"
mv: cannot stat 'ubinize_normal.cfg': No such file or directory
WARNING: blah/tmp/work/blah/core-image-base/1.0-r0/temp/create_image.multiubi:1 exit 1 from
mv ubinize${vname}.cfg blahtmp/deploy/images/blah/
(From OE-Core rev: bc7643846f9fcef13a02f9299faa5454c843e8b1)
Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/package_rpm.bbclass')
0 files changed, 0 insertions, 0 deletions