Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upUnexpected "could not canonicalize path" warnings in proxies when on a network drive #682
Comments
brson
referenced this issue
Aug 23, 2016
Closed
rustc can't find dependencies when building in a VirtualBox shared drive on a Windows VM #2990
This comment has been minimized.
This comment has been minimized.
|
In the original report, drive Maybe we can detect when the drive is a network drive and not emit the warning, as a known case. Or maybe the warning is not worth printing at all. |
brson
changed the title
Unexpected "could not canonicalize path" warnings in proxies
Unexpected "could not canonicalize path" warnings in proxies when on a network drive
Aug 23, 2016
Diggsey
added this to Error messages & documentation
in Issue Categorisation
May 4, 2017
Diggsey
referenced this issue
May 4, 2017
Closed
Multiple "warning: could not canonicalize path" at start of any tool invocation #999
Diggsey
added
bug
help wanted
labels
May 4, 2017
This comment has been minimized.
This comment has been minimized.
Scondo
commented
Mar 19, 2019
|
Same problem with ram drive... up to block of compilation. |
This comment has been minimized.
This comment has been minimized.
|
If you bypass rustup and run the compiler/cargo directly, are you able to compile/whatever? If so, then it's worth trying to bypass this in rustup, if the compiler or cargo also suffer then perhaps it'd be better as a bug against |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
brson commentedAug 23, 2016
Original report rust-lang/cargo#2990 (comment)
When running
cargo runinsideE:\hello_worldcargo is printing warnings likeThat's pretty surprising since there's nothing interesting about that path.