Hi all,

I recently upgraded my project from dunfell 3.1.5 to 3.1.6 and saw
errors about pseudo path mismatches on various build machines. Removing
TMPDIR solved the problem, but I did some digging to see if I find the
source of the problem.

First of all: The wiki page about pseudo aborts [1] is generally a good
thing, I hope it gets higher into search machines result lists as time
passes (a week ago I didn't find it at all, now it's result #4 on
Google for "yocto exit code 134" which is okay).

Second, a nice message was added to sanity.bbclass that the user should
clean the TMPDIR and rebuild. Sadly, an override of the OELAYOUT_ABI
variable in meta-poky/conf/distro/poky.conf suppressed this message for
dunfell 3.1.6. It's fixed in the branch for 3.1.7 (the offending code
was removed).

# $OELAYOUT_ABI [2 operations]
#   set /workdir/build/../layers/poky/meta/conf/abi_version.conf:7
#     "14"
#   set /workdir/build/../layers/poky/meta-
poky/conf/distro/poky.conf:76
#     "12"
# pre-expansion value:
#   "12"
OELAYOUT_ABI="12"

Maybe we should add a section about that bug which suppresses the
message and that emptying the TMPDIR is recommended when updating to
3.1.6 from an older release to the wiki page?

I haven't checked if this also affects other versions.

[1]: https://wiki.yoctoproject.org/wiki/Pseudo_Abort

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53170): https://lists.yoctoproject.org/g/yocto/message/53170
Mute This Topic: https://lists.yoctoproject.org/mt/82208141/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to