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

["Yoann Congal" <yoann.congal@smile.fr>]

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?

>
> ERROR: Logfile of failure stored in: /home/jpsaman/Source/xxxxx/insight_test3/build-raspberrypi4-64/tmp/work/cortexa72-poky-linux/miniflex-generate-salt/1.0/temp/log.do_package.21002
> ERROR: Task (/home/jpsaman/Source/xxxxx/insight_test3/sources/meta-xxxxx/recipes-applications/miniflex-generate-salt/miniflex-generate-salt.bb:do_package) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 1789 tasks of which 1775 didn't need to be rerun and 1 failed.
> NOTE: Build completion summary:
> NOTE:   do_populate_sysroot: 0.0% sstate reuse(0 setscene, 1 scratch)
> NOTE:   do_deploy_source_date_epoch: 0.0% sstate reuse(0 setscene, 1 scratch)
> NOTE:   do_deploy_archives: 0.0% sstate reuse(0 setscene, 1 scratch)
> NOTE:   do_recipe_qa: 0.0% sstate reuse(0 setscene, 1 scratch)
> NOTE:   do_package: 0.0% sstate reuse(0 setscene, 1 scratch)
> NOTE:   do_populate_lic: 0.0% sstate reuse(0 setscene, 1 scratch)
> NOTE: Writing buildhistory
> NOTE: Writing buildhistory took: 1 seconds
>
> Summary: 1 task failed:
> /home/jpsaman/Source/xxxxx/insight_test3/sources/meta-xxxxx/recipes-applications/miniflex-generate-salt/miniflex-generate-salt.bb:do_package
> Summary: There was 1 ERROR message, returning a non-zero exit code.
>
> —
> Kind regards,
> Jean-Paul Saman


-- 
Yoann Congal
Smile ECS