-
Notifications
You must be signed in to change notification settings - Fork 543
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
PPPort breaks the build from sources of 5.32 on Ubuntu18.04 (WSLv1) #18252
Comments
This is strange, I'm not sure why the test need to be executable. @khwilliamson any ideas what went wrong there? Note that since v5.33.1 dynamic tests from PPPort are not shipped anymore and this file |
No clue. @pali any ideas? |
I guess that problem is with write permissions. mktests.PL cannot create file You could try to add permissions: |
It generates the object files in-tree without a problem, so it should have write permissions in perl sources directory. But I'll try this out. |
The same error is produced on v5.33.1. after chown and re-launching |
As I said, I have already seen this problem in WSL and I suspect that there is a bug in WSL permission layer. |
Maybe. Just for information, before the build the permissions seem identical:
I wonder if permissions get changed somehow. I'll see if they change after the build |
What happens is:
From strace:
Indeed, this fails as well: |
This fails as well: |
This looks strange enough, reporting to WSL, let's see |
Exactly same issue which I have already seen in other projects.
Let us know if you get some information. Thanks! |
A-ha! I found that this file is somehow write-protected: By that point where it is generated:
|
That's why WSL doesn't want to truncate or open it for writing |
Why would it be write-protected? |
It seems that the |
Yep, basically Perl build process wants to open as write-only/truncate already existing readonly files. Why is that happening? Is it still a WSL's problem that it fails? Is it supposed to work in Linux "proper"? To me it looks a correct behavior |
Hi. I just wanted to add that I'm experiencing the exact same issue when building perl 5.32.0 on HP-UX (IA-64). |
I don't see the problem working with the tar extracted tree, but that has the same modification time for
I expect your copy of the tree is giving one or more of those dependencies a later modification time than Do you still see the problem if you "touch" If this does fix the problem I think it's a case of the build process being a bit too fragile in the tarball, and should be fixed at our end, possibly by only having the rule to regenerate the tests if |
Did you try out this suggestion? If not could you? |
I ran into this same issue while building perl 5.32.1 from a tarball. I can confirm that the following workaround avoids the issue when invoked before running
|
I believe this was fixed by c8799af which removed the test files from the tarball, so they are always generated and are writable. Do you see this problem with 5.34 and later? |
Personally I am no longer able to try and reproduce the issue, so I can't give you relevant input whether or not it persists. |
Same for me - I moved on from this, I think it stopped reproducing at some point, but I didn't investigate why. So I'll close this issue. But if anyone stumbles on it again, please mention me an I will reopen it again! |
I'm running the following script on Ubuntu 18.04 / WSLv1 / case-sensitive mount point. It produces the following error:
Full log: log.zip
P.S. Can one also configure perl / modules build to skip tests?
Thank you!
The text was updated successfully, but these errors were encountered: