]> code.ossystems Code Review - openembedded-core.git/commit
update_udev_hwdb: clean hwdb.bin
authorMingli Yu <mingli.yu@windriver.com>
Fri, 30 Oct 2020 09:02:04 +0000 (17:02 +0800)
committerAnuj Mittal <anuj.mittal@intel.com>
Thu, 12 Nov 2020 03:54:28 +0000 (11:54 +0800)
commit93e59a78da3dab56c91f423b2c0f29a8ebaf2700
treeb6c4f6ed99c918bdad68153ae5f3411ff8bfc05f
parenta76d66feae7050d5d59964108a065bc6251667eb
update_udev_hwdb: clean hwdb.bin

Steps to reproduce:
echo "IMAGE_INSTALL_append = \" udev-hwdb lib32-udev-hwdb\"" >> conf/local.conf

When install both udev-hwdb and lib32-udev-hwdb as above,
there comes below do_populate_sdk error:
 $ bitbake core-image-sato  -c populate_sdk
 ERROR: Task (/path/core-image-sato.bb:do_populate_sdk) failed with exit code '134'
 NOTE: Tasks Summary: Attempted 5554 tasks of which 0 didn't need to be rerun and 1 failed.

 $ cat /path/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r5/pseudo/pseudo.log
 [snip]
 inode mismatch: '/path/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0-r5/sdk/image/usr/local/oecore-x86_64/sysroots/core2-64-poky-linux/lib/udev/hwdb.bin' ino 427383040 in db, 427383042 in request.
 [snip]

It is because both udev-hwdb and lib32-udev-hwdb will generate
${SDK_OUTPUT}/${SDKTARGETSYSROOT}/lib/udev/hwdb.bin during do_populate_sdk
and it triggers pseudo error.

So clean hwdb.bin before generate hwdb.bin to avoid conflict to
fix the above do_populate_sdk error.

(From OE-Core rev: c7472925feb53ce92c1799feba2b7a9104e3f38f)

Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 994ca65e6f828dd38e0d7d09fb5243147ba4e36b)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
scripts/postinst-intercepts/update_udev_hwdb