You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mount a network drive from a Linux samba share, in my case as D:
make D: accessible within WSL: sudo mount -t drvfs D: /home/user/dev
clone sdl-zig-demo into this directory and try to compile it with zig build
I get the output (added some line breaks to improve readibility):
% zig build
install
└─ install sdl-zig-demo failure
error: unable to update file from
'/home/user/dev/sdl-zig-demo/.zig-cache/o/31b7da78f2ea68584a39395618fa7226/sdl-zig-demo' to
'/home/user/dev/sdl-zig-demo/zig-out/bin/sdl-zig-demo': PermissionDenied
Build Summary: 1/3 steps succeeded; 1 failed (disable with --summary none)
install transitive failure
└─ install sdl-zig-demo failure
error: the following build command failed with exit code 1:
/home/user/dev/sdl-zig-demo/.zig-cache/o/7ea22ec676a64f02709f55d4496cc1dd/build
/opt/zig-linux-x86_64-0.13.0/zig
/home/user/dev/sdl-zig-demo
/home/user/dev/sdl-zig-demo/.zig-cache
/home/user/.cache/zig
--seed 0x348388c2 -Zab712fe6bccacd35
After spending quite some time to figure out what is wrong with permissions, as the file can be manually copied without any issues, strace revealed that the issue is not with the copy itself:
It is probably due to the combination of wsl+network drive.
Expected Output
Not quite sure, but it would be useful to indicate that this is not due to the actual directory/file permissions and have something to do with the setup itself
The text was updated successfully, but these errors were encountered:
Zig Version
0.13.0
Steps to Reproduce and Observed Output
sudo mount -t drvfs D: /home/user/dev
zig build
I get the output (added some line breaks to improve readibility):
After spending quite some time to figure out what is wrong with permissions, as the file can be manually copied without any issues,
strace
revealed that the issue is not with the copy itself:It is probably due to the combination of wsl+network drive.
Expected Output
Not quite sure, but it would be useful to indicate that this is not due to the actual directory/file permissions and have something to do with the setup itself
The text was updated successfully, but these errors were encountered: