Basically all cargo commands fail

[nemonical]

I really don't know if this is an appropriate place to ask, but I hope I'll get this resolved either way,
cargo build fails to run with the error

error: failed to run custom build command for `proc-macro2 v1.0.94`

Caused by:
  could not execute process `/mnt/data/Programming/Rust/utracker/target/debug/build/proc-macro2-0c7b5b29af8b7aee/build-script-build` (never executed)

Caused by:
  Permission denied (os error 13)

I understand this, because the build process is managed by nix, but:
Commands like cargo doc, cargo check and cargo test also fail and there's no nix equivalent afaik.
So how do I use this functionality? Are these commands supposed to fail?

[90-008]

i'm not sure if i understand, is this an error while building the nix derivations? or is it when building in a devshell? if the latter i can't really be sure why because i don't know your exact setup but permission denied sounds pretty self explanatory (unless you did check it and the permissions look fine?)

[nemonical]

I've figured out the reason and it's incredibly annoying.
All my coding work is on a mounted drive on an NTFS partition so I can read the data from Windows too, if I need to.
(also so that reinstalling the os won't destroy any data)
But NTFS doesn't support setting ownership in the same way that ext does or something and so cargo refuses to run the build scripts!
I just tried running it in home and it worked, so that must be it.
I guess I'm gonna shrink the NTFS partition, create an ext4 partition, and move my stuff over, because I really really don't want to lose it by reinstalling the os and I don't have a NAS yet.

[90-008]

oh that makes sense yeah. i'd probably recommend using btrfs because there is a driver for windows (winbtrfs), i used to daily drive that for 2 years and it worked pretty well

[nemonical]

hmm. I've tested it now with an actual EXT4 partition, in a folder that I gave myself ownership over, and it still won't run cargo doc, unless it's in my home directory. I even used chmod to set all the permissions to be the same as ~.
I'm gonna try all the different test rust environments I've made now, i guess