-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Issue with zef installs on windows #452
Comments
|
I was able to install Directory::Tree from a git clone at one point during this testing; it appears to require installing from the ecosystem to generate the error. |
What if you use —/rea ? |
ok, that worked. |
I suspect the precomp paths its trying to save to is too long when using rea (which has longer names than other ecosystems). It might require something like https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ In your example the path is |
What does --/rea do? (Or, I suppose: what is rea?) |
ah, https://github.com/Raku/REA. Thanks, @ugexe |
Related issue that --/rea didn't help with:
|
If you think this is still the windows filename length; is this maybe a rakudo thing we can do to reduce length of precomp file names in general? (shorter guids, fewer non guid path components?) |
Right, REA just uses the longest file names and thus ends up in the longest temp directory name. As far as what rakudo can do yeah sure we can remove path parts, but that is just moving the issue up a (probably insignificant) amount. Honestly I'm not sure why this issue occurs though, as I'm pretty sure libuv uses the UNC paths as shown here which should have a much longer limitation. |
I've enabled support for long paths on windows (via the registry, and post-reboot), and am still getting failures trying to install IO::Capture::Simple - no failures if I clone that repo and do a |
You might try actually creating the path that is causing the problem with a raku one-liner to see if it works |
Related to MoarVM/MoarVM#1745. I'm getting this failure on many items that would (probably) otherwise install no problem. |
After reinstalling rakudo a few times, and updating zef, my zef install now consistently fails with any installed version of rakudo, even after wiping out the entire install directory and re-installing moar/nqp/rakudo/zef.
I've tried now with clean rakudo/zef installs with both HEAD and 2022.04 and am getting the same errors trying to install modules.
Please see labster/p6-file-directory-tree#20 for an example. This is also happening on JSON::Marshal.
The text was updated successfully, but these errors were encountered: