Cannot lock file on lustre filesystem

When I tried to install Cargo and Rust under a lustre filesystem using rustup I got the following error after trying to build a simple crate:

$ cargo run
error: failed to lock file: ~/simple_crate/Cargo.lock

Caused by:
  Function not implemented (os error 38)

It would be nice to let Cargo handle missing flock() by not locking? (durka42)

[alexcrichton]

Sounds good to me! I believe the relevant support would go here. Would you be interested in sending a PR for this?

I would need some mentoring, but sure!

[alexcrichton]

Sure yeah I'd be happy to help! I think you'll basically want to add a clause like the existing one for OSX except which matches the error code coming out of libc. I don't know precisely what 38 is but you can likely find what it is in the libc crate.

[alexcrichton]

Hm not sure I understand, can you elaborate?

I'm not sure how to start

[alexcrichton]

Oh sure yeah, so to start out you'll want to compile from source to ensure that's working. After that you can likely run cargo test to ensure all tests are passing.

Once that's all taken care of you can toy around modifying the relevant match block and see if that fixes tests for you.

If that's all working, then you can send a PR!

ok i found 38

https://doc.rust-lang.org/libc/x86_64-unknown-linux-gnu/libc/constant.ENOSYS.html

so it would be something like

#[cfg(target_os = "linux")]
Err(ref e) if e.raw_os_error() == Some(libc::ENOSYS) => return Ok(()),

[alexcrichton]

Ah yeah that looks right! (for a constant to check against)

That would be enough? or there is something else to be done?

Someone told me that it would be nice to check the filesystem, but I'm not sure how to do it

[alexcrichton]

In theory that's it, but you may want to test out the cargo binary locally to ensure you don't get the same error

Ok, I have a logistical problem. I cannot build Cargo because it needs a previous rustc/cargo installation and it wont build because the filesystem cannot lock files

#3437

[alexcrichton]

Heh that would indeed cause problems! Could you build it in /tmp perhaps which may not be the same filesystem?

Almost there. However the cargo registry is still in my home folder on lustre, how can I change this path?

[alexcrichton]

Oh you can probably do CARGO_HOME=/tmp/cargo

It failed:

note: /usr/bin/ld: /tmp/make_temp/cargo/target/release/deps/libopenssl_sys-59e7705a3169e032.rlib(s23_meth.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
/tmp/make_temp/cargo/target/release/deps/libopenssl_sys-59e7705a3169e032.rlib: could not read symbols: Bad value
collect2: ld returned 1 exit status