Re: [yocto] Pseudo abort errors

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2025-06-03 at 00:40 -0700, arthur52666 via lists.yoctoproject.org wrote:
> 
> I am building Embedded Linux image based on Yocto framework. The image building involves a lot of recipe execution.
> when building the image I always get below pseudo abort error :
>  
> > Pseudo log:
> > path mismatch [1 link]: ino 147610407 db '/tmp/sh-thd.VPxkGG' req '/tmp/sh-thd.4Z7cxB'.
> >  
>  
> I tried to build the image multiple times, 100% got the error every
> time, but the error was reported at different recipe every time. I've
> read the wiki page about them, but I'm not sure exactly what we are
> doing wrong that is making this happen. The files listed in the error
> log should be shell tmp files.
[...]
> Some context here: 
> 1. I are running Yocto build command inside a docker container, rather than a metal Linux server
> 2. I saw the pseudo abort error reported at multiple recipes such as autoconf-native, ncurses 
> 3. The same error was still reported when executing Yocto build command to do single recipe build.
>  
>  
> Thanks for your time and any suggestions.

I suspect the issue is the filesystem setup your docker container is
using. Bitbake/OE's use of pseudo assumes stable inode numbering and
some forms of container filesystems can break this assumption. I'm
afraid I don't remember specifically which setups don't work but others
might. That would certainly be the area I would look.

If the errors are always on the same filesystem location (/tmp?) then
that would hint at which filesystem to look at too.

Cheers,

Richard