microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.29k stars 814 forks source link

"semop(1): encountered an error: Function not implemented" in fakeroot under qemu #8198

Closed mforkel closed 1 month ago

mforkel commented 2 years ago

Version

Microsoft Windows [Version 10.0.19044.1586]

WSL Version

Kernel Version

5.10.60.1

Distro Version

Debian 11 (Bullseye)

Other Software

libc-bin 2.31-13+deb11u2 qemu-user-static 1:5.2+dfsg-11+deb11u1 fakeroot 1.25.3-1.1 pbuilder 0.231

Repro Steps

I build packages for armhf on an am64 host with pbuilder and qemu (qemu-user-static). This works in the Debian distro (both with Buster and Bullseye) for packages for Raspbian Buster. But it fails when I try to build packages for RPi OS Bullseye with

$ DIST=rpi-bullseye pdebuild
...
dpkg-buildpackage: info: host architecture armhf
 fakeroot debian/rules clean
semop(1): encountered an error: Function not implemented
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 1

I do not encounter that problem with the same pbuilder configuration in a regular installation of Debian Bullseye. A problem resulting in the same error was fixed in qemu 1:5.0-9.

Expected Behavior

No error in fakeroot

Actual Behavior

Error in fakeroot

Diagnostic Logs

No response

0x000000FF commented 1 year ago

I got the same error when I try to build the example image,did you solved the problem?How did you do ?thanks

Biswa96 commented 1 year ago

Is it possible to use WSL2 instead?

mforkel commented 1 year ago

Sorry for the late reply

did you solved the problem?How did you do ?

Unfortunately, I didn't solve it

Is it possible to use WSL2 instead?

I got the same error with WSL 2 and Debian Bullseye (versions at the time I tested: pbuilder 0.231, fakeroot 1.25.3-1.1, qemu-user-static 1:5.2+dfsg-11+deb11u1 and libc-bin 2.31-13+deb11u2)

microsoft-github-policy-service[bot] commented 1 month ago

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!