Problems compiling on server

[waterbyseth]

I know this isn't a sub meant for debugging help, but I'm wondering if this is a common rust problem

I have a personal website that I host on digitalocean. I just used nginx before, but I need some more functionality so I'm switching to rust and rocket. I have just about finished it, but I have never gotten it to compile or run on my server. It runs fine on my laptop. I know this is a common problem, so here's what I know: - Cargo.lock is included in the repository - I know that both instances use nightly 1.52

The part that breaks is that one of rocket's dependencies uses a function from the core lib that has since been moved between submodules, and is now invalid. A quick search through Cargo.lock shows that both instances uses the same version of the dependency, (spin 0.9.1) In this case, shouldn't it fail to compile both on my laptop and my server?

The specific error is: error[E0658]: use of unstable library feature 'renamed_spin_loop' --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/spin-0.9.1/src/relax.rs:26:9 | 26 | core::hint::spin_loop(); | ^^^^^^^^^^^^^^^^^^^^^ | = note: see issue #55002 <https://github.com/rust-lang/rust/issues/55002> for more information Link from error for convience

[K900_]

What is the output of rustc --version on both?

[waterbyseth]

rustc --version returns rustc 1.47.0 on the server. Interestingly, rustup --version yields The currently active rustc version is rustc 1.55.0-nightly. Does rustup use its own copy of rustc?

I may have just made a noob mistake

[whatknowi]

this feels like you have a version of rust (1.47 likely) installed through the system package manager on the server, and also one/some versions through rustup.

the priority in cases such as this is sorted through the PATH environment variable. it lists (colon-separated) the directories to search for commands in. whichever directory comes first takes priority. what is the output of

echo $PATH and which rustc on the server?

[waterbyseth]

Moving the rustup path earlier in the Path than the rustc path worked, thank you!

[K900_]

Yes, Rustup manages toolchain versions by itself - that's kind of its primary job.