8582 2015-10-26 21:22:10 +0000 Error message not in log file 2022-12-08 16:18:19 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 1.7.4 x86 Multiple RESOLVED WONTFIX Medium normal 4.99 1 juro.bystricky unassigned liezhi.yang meta.mr.watcher meta.watcher mingli.yu randy.macleod richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 55786 0 juro.bystricky 2015-10-26 21:22:10 +0000 run bitbake core-image-minimal using the same setup as in https://bugzilla.yoctoproject.org/show_bug.cgi?id=8581. an error message is briefly displayed: ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. This message is not logged in any file and if you blink, you will miss it, it gets overwritten on console as well. Observed with dizzy, fido and master. 66920 1 bluelightning 2016-10-05 04:13:40 +0000 Juro, do you think this one is fixed with the recent pseudo patch (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7aba4c930e94316a90ada6022792ecb00ff2cf86 )? 66946 2 juro.bystricky 2016-10-05 16:25:56 +0000 (In reply to comment #1) > Juro, do you think this one is fixed with the recent pseudo patch > (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/ > ?id=7aba4c930e94316a90ada6022792ecb00ff2cf86 )? Depends how you define "fixed". If this is a pseudo error message, it should now end up in the pseudo error log. As the message explicitly says ERROR:...ignored, something else will eventually break (not being able to install correctly). So not being able to even glimpse the message may actually obfuscate the failed install even more. So IMHO the message should be made more prominent, not less. (Unless the pseudo log is parsed for errors at some point) Typical error will be something like: (see https://bugzilla.yoctoproject.org/show_bug.cgi?id=8581 ) chown: changing ownership of 'xxx': Operation not permitted So the root cause of the error is not obvious. However fixing it is quit simple: set NO32LIBS = "0" in local.conf. Having said this, it is very unlikely anyone will encounter this error with 2.1 and later. 82359 3 randy.macleod 2018-11-29 16:13:25 +0000 Mingli, The goal here is to ensure that if this error happens, that the root cause is reported clearly. Richard has suggested that you make a change to deliberately introduce a libpseudo error and then work on fixing the capture and reporting of such a fundamental error. Ask on the list if you need more guidance. 88719 4 richard.purdie 2020-12-03 16:13:25 +0000 We need to test this and see if it is still an issue... 94507 5 randy.macleod 2022-12-08 16:18:19 +0000 We added more logs to deal with the errors in inode mismatches but this error message is client-side in pseudo. A better diagnostic or early check would be good.