Skip to main content
Associate
July 24, 2026
Question

OpenSTLinux 5.0.8: build-info-openstlinux do_package fails under pseudo with "unknown base path for fd" while manual tar succeeds

  • July 24, 2026
  • 1 reply
  • 25 views

Hi ST Team,

I am facing an issue while building an OpenSTLinux project for STM32MP255.

Environment

  • Board: STM32MP255
  • OpenSTLinux: 5.0.8
  • Yocto Distribution: openstlinux-weston
  • Ubuntu: 22.04 LTS
  • Kernel: 6.8.0-124-generic
  • pseudo version:

    1.9.0+git
  • pseudo SRCREV:

    28dcefb809ce95db997811b5662f0b893b9923e0

 

Problem

The build fails during:

build-info-openstlinux.bb:do_package

The failure occurs inside Yocto's standard perform_packagecopy() while executing:

tar --exclude=./sysroot-only \
-cf - \
-C image \
-p -S . |
tar -xf - \
-C package

The error is:

got *at() syscall for unknown directory, fd 4
unknown base path for fd 4, path build
couldn't allocate absolute path for 'build'
tar: ./etc/build: Cannot open: Bad address
tar: Exiting with failure status due to previous errors

 

Investigation Performed

I verified the following:

1. Recipe

The build-info-openstlinux.bb recipe is unchanged and only creates the /etc directory.

The /etc/build file is generated by image-buildinfo.bbclass.

2. Generated file

Verified that:

image/etc/build

exists.

Also checked:

file image/etc/build

Output:

ASCII text

The file permissions and ownership are normal.

3. Manual tar test

I manually executed the exact command used by perform_packagecopy():

rm -rf package
mkdir package

tar --exclude=./sysroot-only \
-cf - \
-C image \
-p -S . |
tar -xf - \
-C package

Result:

echo $?
0

The file:

package/etc/build

is copied successfully.

Therefore, the tar command itself works correctly outside BitBake.

4. pseudo rebuild

Rebuilt pseudo:

bitbake pseudo-native -c cleansstate
bitbake pseudo-native

Build completed successfully.

5. build-info rebuild

Also rebuilt:

bitbake build-info-openstlinux -c cleansstate
bitbake build-info-openstlinux

The failure still occurs during do_package.

Observation

The exact same tar command:

  • succeeds when executed manually,
  • fails only when BitBake executes it under pseudo.

This suggests the problem may be related to pseudo handling of directory file descriptors during do_package().

 

Questions

  1. Is this a known issue with the pseudo version shipped in OpenSTLinux 5.0.8?
  2. Is there an official patch or updated pseudo recipe available?
  3. Has this issue already been fixed in a newer OpenSTLinux release?

 

Any guidance would be greatly appreciated.

Thank you.

1 reply

Olivier GALLIEN
ST Technical Moderator
July 24, 2026

Hi ​@Rajsingh_ 

We indeed received similar feedback. 

This is due to the system upgrade. In Ubuntu daily usage, it is very common to do the system upgrade. In my Ubuntu PC, the tar version is upgraded from 1.35+dfsg-3build1 to 1.35+dfsg-3ubuntu0.3.

1.35+dfsg-3build1 --> OK, Yocto compilation success.

1.35+dfsg-3ubuntu0.3 --> KO, Yocto compilation fail.

You may need to check if the tar version is the latest one to reproduce this issue.

Else the issue is not seen with latest OSTL 6.2.1 

Olivier 

 

Olivier GALLIEN In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Rajsingh_Author
Associate
July 25, 2026

Hi Olivier,

Thank you for your response and for looking into this.

I checked my environment, and it appears the issue was indeed related to the interaction between the newer host tools and the older pseudo version shipped with OpenSTLinux 5.0.8.

In my case, I backported a newer pseudo recipe from a recent OpenEmbedded release into my BSP while keeping the same Ubuntu host environment. After rebuilding pseudo-native and rebuilding the image, the packaging issue was resolved and I was able to build the image successfully.

Thank you again for your guidance.