-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[22.03] tools/pkgconf: meson: OSError: [Errno 5] Input/output error: 'selinuxenabled' #10609
Comments
|
Input/output error: 'selinuxenabled'
@bersbersbers can you share output of |
@ynezz sure, see below! I don't see
Happy to help debugging further, but I don't see any immediate culprit and I don't really want to bisect this whole tree up there. |
Related: mesonbuild/meson#10774 That is very strange. |
Found the issue: https://github.com/mesonbuild/meson/blob/master/mesonbuild/minstall.py#L236 I think this is a problem with WSL. Input/Output Error is the wrong thing to report when the "selinuxenabled" binary is missing. edit: add a new file, tools/meson/patches/010-wsl.patch with the contents:
|
I tried to reproduce on WSL1 18.04 and 20.04. Couldn't do it. The only potential issues I can think of are: old Windows 10, old Ubuntu packages (sudo apt update;sudo apt upgrade), or some weird fs setup. Are you running WSL1 or 2? |
I still can, so let's see if I can help.
Nope - 21H2.
TLDR: did not fix the issue. Okay, so I went ahead to repro this quickly:
That now gives the same error again. Then:
Same thing! For the record:
Now,
Still, same Related: https://github.com/python/cpython/blob/3.8/Lib/subprocess.py#L1678-L1704
I am not aware of anything.
2:
This looks like a useful given, given my output of By the way, |
yet I don't get the pkgconf error... weird. I'm running WSL1 though. IIRC WSL2 was using some plan9 thing. Forgot the details... Did the patch fix it? edit: ah I can't read. Mine throws FileNotFoundError, which meson handles. |
Looks like it, yes! |
I'm still curious. What's the filesystem of the directory? (cat /proc/mounts) IOError indicates a bad driver. |
Not sure what all of this is, but I guess these two are relevant:
Interestingly, today, I get only this, in the same directories I tried before:
Strange indeed. |
As in the upstream PR, I'm blaming 9p for this. WSL1 does not use it. |
Yet, after building once more, I see this - in the same WSL session as before:
Again, the |
as upstream merged the fix, do you want this backported? |
is there any other way to fix this? |
Avoid WSL2? |
@neheb this is strange. wsl2 use plan9 from windows to expose wsl2 directory but internally it's just a plain ext4 in a vm... (as you can see from /proc/mounts) Wonder if I can try to repro this and check if this bug is not fixed on new version of wsl2 |
For the record, I'm building in WSL2 only for a long time already, using Debian Buster and Bullseye, and recently switched to Alpine 3.16 for the 22.03 branch. I'm getting no such errors in either distro. All my distros are prepared as described in the "build system setup" wiki entry, including trimming the PATH, since (sadly) no one yet felt like chasing the quotation bug that causes build failures with blanks in the PATH, that appeared sometime after 19.07. So yes, clear repro steps would help to find the actual cause, since "it's WSL2" alone doesn't look like being the cause. P.S. As Ansuel says, WSL2 is using normal ext4 in its VHD, not 9P. Only WSL1 is using some non-standard (fake) FS due to its non-VM nature. P.P.S. WSL1 is working perfectly fine for me to build 22.03 as well - it's just painfully slow due to the additional interfacing layer on its fake FS. |
@Shine- that's not why it's slow: microsoft/WSL#873 (comment) . It's windows itself. @Ansuel since this was merged this can be closed. |
The text was updated successfully, but these errors were encountered: