Re: [yocto] Howto solve pseudo abort issue? #bitbake #fakeroot #linux #raspberrypi #scarthgap

[Jean-Paul Saman <jean-paul.saman@m2x.nl>]

On 7/10/26 10:45, Yoann Congal wrote:
> On Fri Jul 10, 2026 at 10:34 AM CEST, Jean-Paul Saman via lists.yoctoproject.org wrote:
>> The problem:
>>
>> Our yocto build system suddenly started failing on ‘do_package’ due to a pseudo abort issue. Even packages that have not been changed recently. The same happened on my local development system.
>>
>> Searching in Yocto discussions or other sources did not provide a solution that works in our case. I tried the following solutions (NOTE: this package was not changed when the problem started):
>>
>> 1. bitbake -c cleanall miniflex-generate-salt && bitbake miniflex-generate-salt
>> 2. bitbake -c cleansstate miniflex-generate-salt && bitbake miniflex-generate-salt
>> 3. examine with bitbake -c devshell miniflex-generate-salt
>> 4. set parallel jobs to '-j 1’ in conf/local.conf
>> 5. remove build/tmp and rebuild entire distribution
>>
>> The logfile suggests there is a path mismatch.
>>
>> I have  2 questions basically:
>>
>> 1. What I do not understand is how this can happen, suddenly without a clear (at least for me) cause?
>> 2. How to solve this situation?
>>
>> ---
> [...]
>> tar: ./usr/share/licenses/miniflex-generate-salt: Cannot mkdir: No such file or directory
>> got *at() syscall for unknown directory, fd 4
>> unknown base path for fd 4, path share
>> couldn't allocate absolute path for 'share'.
>> got *at() syscall for unknown directory, fd 4
>> unknown base path for fd 4, path share
>> couldn't allocate absolute path for 'share'.
>> tar: ./usr/share: Cannot mkdir: Bad address
>> tar: ./usr/share/licenses/miniflex-generate-salt/xxxxx-LICENSE: Cannot open: No such file or directory
>> tar: Exiting with failure status due to previous errors
> 
> Hello,
> 
> That looks like https://bugzilla.yoctoproject.org/show_bug.cgi?id=16143
> I think you just need to upgrade OE-core/poky on a more recent
> scarthgap. Specifically, you want pseudo >= 1.9.4.
> 
> For the explanation, Ubuntu based-distro recently got a tar upgrade that
> add a new syscall that pseudo needs to handle. Some user worked around
> that by changing their host tar version.
> 
> Does that helps?

Yes, it helps. Thanks for the swift reply.

I downgraded tar to the version (1.34+dsfg-1build3) of the official 
release image and Yocto builds our image correctly now. Next version 
I'll upgrade scarthgap to a more recent version, but for now the quick 
fix is preferred.

-- 

Kind greetings,

       Jean-Paul Saman