Hello, I know that this might be an old thread but we seem to deal the exact same issue in our yocto builds, that's why I am writing here. Recently we switched from sumo yocto branch to dunfel. Now some recipes with nothing special in it, just compile and install, are failing in the install phase because of pseudo abort. Those recipes are installing via the do_install some headers files into the usr/include folder and later those headers are share via the sysroot to other recipes.
I read what has been written above but I didn't see a final solution. So I am also trying to understand the error in order to find a solution. If we do a clean build (bitbake lib32-las -c cleansstate) then the recipe compiles fines. But if we invoke the building without the cleasstate the recipe fails in install phase due to pseudo. Install error: -------------------------------------------- + install -m 0644 WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_list.h WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_pdinc.h WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_util.h WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_varmsg.h WORKDIR/lib32-las/M-WBS0.1-r0/image/usr/include abort()ing pseudo client by server request. See https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this. Check logfile: WORDIR/lib32-las/M-WBS0.1-r0/pseudo//pseudo.log Aborted (core dumped) + bb_exit_handler + ret=134 + echo WARNING: exit code 134 from a shell command. WARNING: exit code 134 from a shell command. + exit 134 --------------------------------------------------------------------------------- And pseudo log error output: ------------------------------------------------------------------ pid 26345 [parent 26344], doing new pid setup and server start Setup complete, sending SIGUSR1 to pid 26344. path mismatch [3 links]: ino 7868999 db 'WORKDIR/lib32-las/M-WBS0.1-r0/package/usr/src/debug/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_list.h' req 'WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_list.h'. db cleanup for server shutdown, 08:38:52.482 memory-to-file backup complete, 08:38:52.482. db cleanup finished, 08:38:52.482 debug_logfile: fd 2 pid 6423 [parent 6422], doing new pid setup and server start Setup complete, sending SIGUSR1 to pid 6422. path mismatch [3 links]: ino 7868999 db 'WORKDIR/lib32-las/M-WBS0.1-r0/package/usr/src/debug/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_list.h' req 'WORKDIR/lib32-las/M-WBS0.1-r0/git/lasiflib/include/lasif_list.h'. db cleanup for server shutdown, 09:13:45.899 memory-to-file backup complete, 09:13:45.899. db cleanup finished, 09:13:45.899 ----------------------------------------------------------------------------------------------------------------------------------- I added the export PSEUDO_DEBUG = "nfoPcvdDyerpswikVx" in the recipe but I couldn't understand much. In the whole build we have the RM_WORK enabled but for that current recipe we have excluded it. Also the task order is the following: do_cleansstate (20698): log.do_cleansstate.20698 do_cleanall (22404): log.do_cleanall.22404 do_rm_work (24346): log.do_rm_work.24346 do_fetch (24434): log.do_fetch.24434 do_prepare_recipe_sysroot (24465): log.do_prepare_recipe_sysroot.24465 do_unpack (24466): log.do_unpack.24466 do_patch (24493): log.do_patch.24493 do_populate_lic (24665): log.do_populate_lic.24665 do_deploy_source_date_epoch (24666): log.do_deploy_source_date_epoch.24666 do_configure (24765): log.do_configure.24765 do_compile (24809): log.do_compile.24809 do_install (27477): log.do_install.27477 do_populate_sysroot (27510): log.do_populate_sysroot.27510 do_package (27509): log.do_package.27509 do_packagedata (29544): log.do_packagedata.29544 do_package_qa (29592): log.do_package_qa.2959 do_package_write_ipk (29593): log.do_package_write_ipk.29593 Ok build till now. Next invocation do_prepare_recipe_sysroot (23311): log.do_prepare_recipe_sysroot.23311 do_configure (23769): log.do_configure.23769 do_compile (24132): log.do_compile.24132 do_install (26628): log.do_install.26628 do_install (32535): log.do_install.32535 do_install (4454): log.do_install.4454 do_install (26343): log.do_install.26343 do_rm_work (4905): log.do_rm_work.4905 do_deploy_source_date_epoch (4919): log.do_deploy_source_date_epoch.4919 do_configure (4954): log.do_configure.4954 do_compile (5003): log.do_compile.5003 do_install (6421): log.do_install.6421 All above are failures in do_install phase. You see multiple invocations trying to fix the error and adding more debug. If I don't do a cleansstate or cleanall the recipe is not building. We do not delete or manipulate any files in the WORKDIR folder. We might only *copy* some files after the end of the build in some folders outside of yocto. So the WORKDIR structure remains untouched from our actions. In sumo branch we did not have those issues. So something seems to have been changed in between. Right now the dunfell used branch is dunfell-23.0.21 and the latest is dunfell-23.0.22 but I don't see a pseudo fix or something similar. I could also use RM_WORK to that recipe and clean it after build, so the error would disappear but it would be good to understand what is the problem here. If requested I can also sent the full log of install along with the pseudo debug output. Rusty Howell did you solve your problem and how? Thanks a lot, Any suggestions would be highly appreciated, Panagiotis Tamtamis
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59291): https://lists.yoctoproject.org/g/yocto/message/59291 Mute This Topic: https://lists.yoctoproject.org/mt/91650136/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
