Skip to content
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

Lock file error (OS X) #943

Closed
Kerollmops opened this issue May 19, 2016 · 10 comments
Closed

Lock file error (OS X) #943

Kerollmops opened this issue May 19, 2016 · 10 comments

Comments

@Kerollmops
Copy link

For the moment I am fighting with multirust/rust/cargo, trying to compile rust-clippy in nightly 😢
I get this f*cking error, and don't know why (stable works fine but I need nightly)

error: failed to lock file: /.../Documents/rust-clippy/Cargo.lock

Caused by:
  Operation not supported (os error 45)
@oli-obk
Copy link
Contributor

oli-obk commented May 19, 2016

Have you checked if there are any cargo or rustc processes still running? Maybe they crashed/froze. Not sure if OSX has that, but try killall cargo until you get something like no processes found. Then delete the Cargo.lock and try again with cargo build.

@Kerollmops
Copy link
Author

There were no processes still running (killall cargo/rust) and when I delete the Cargo.lock file, I get this error:

error: Unable to update registry https://github.com/rust-lang/crates.io-index

Caused by:
  failed to lock file: /.../.multirust/toolchains/nightly/cargo/registry/index/jackfan.us.kg-1ecc6299db9ec823/.cargo-index-lock

Caused by:
  Operation not supported (os error 45)

@oli-obk
Copy link
Contributor

oli-obk commented May 19, 2016

have you run multirust or cargo with root at any point? that might have ended up creating files owned by root and thus you can't access them now.

@Kerollmops
Copy link
Author

No, never I don't have the root permissions.
That's not a permission problem, I think, because if I use a stable rust version (multirust override stable), the compilation starts and I get no errors until compiling Clippy itself...
stable cargo build output

@Kerollmops
Copy link
Author

Kerollmops commented May 19, 2016

Ho ! I am on an nfs file system if that can help...

NFS parameters: vers=3,tcp,port=2049,nomntudp,
hard,intr,noresvport,negnamecache,callumnt,nolocks,
quota,rsize=65536,wsize=65536,readahead=16,
dsize=4096,nordirplus,nodumbtimr,timeo=10,
maxgroups=16,acregmin=5,acregmax=60,
acdirmin=5,acdirmax=60,nomutejukebox,nfc,sec=sys

@mcarton
Copy link
Member

mcarton commented May 19, 2016

This does not look like it’s Clippy’s fault. Cargo has had some problems with nfs on apparently, and it has been “fixed” on Linux, but not OS X. Maybe you should report it there.

@Kerollmops
Copy link
Author

By adding this link here, this issue is now visible on the this Cargo issue 👍

@mcarton
Copy link
Member

mcarton commented May 19, 2016

That's not a permission problem, I think, because if I use a stable rust version (multirust override stable), the compilation starts and I get no errors until compiling Clippy itself...
stable cargo build output

Clippy can’t be built nor used with a non-nightly compiler.

By adding this link here, this issue is now visible on the this Cargo issue 👍

But no one there has been notified of that.

@Kerollmops
Copy link
Author

Kerollmops commented May 19, 2016

Yup, but cargo/rust starts the compilation and give me these logic errors, not a lock file error, it starts compiling in other words...

@mcarton
Copy link
Member

mcarton commented May 20, 2016

Closing as Cargo’s team has made a PR for that. Feel free to open an new issue if anything is still wrong after it has been merged.

@mcarton mcarton closed this as completed May 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants