Rust does not work after successful install

[HermannSW]

For building a project I need to install Rust toolchain.
I followed the instructions and installation was good:
https://rustup.rs/#

Code: Select all

pi@raspberrypi3BplusX:~ $ curl https://sh.rustup.rs -sSf | sh
info: downloading installer
...
Rust is installed now. Great!

To get started you need Cargo's bin directory ($HOME/.cargo/bin) in your PATH 
environment variable. Next time you log in this will be done automatically.

To configure your current shell run source $HOME/.cargo/env
pi@raspberrypi3BplusX:~ $ 

But even the simplest hello world compilation with rustc hangs infinitely in Raspbian Stretch:

Code: Select all

$ cat hello.rs 
fn main() {
    println!("Hello World!");
}
$ rustc hello.rs 

I did reboot just to see whether it made a difference to just running the source command, but it did not.
Was anybody successful in installing Rust toolchain in Raspbian and getting rustc compiling?

[HermannSW]

I asked on rust forum as well, and got some help:
https://users.rust-lang.org/t/why-does- ... etch/22760

Summary:
While latest stable rustc binary hangs on Raspbian, latest nightly works:

Code: Select all

pi@raspberrypi3BplusX:~ $ /home/pi/.rustup/toolchains/nightly-armv7-unknown-linux-gnueabihf/bin/rustc hello.rs 
pi@raspberrypi3BplusX:~ $ ./hello 
Hello World!
pi@raspberrypi3BplusX:~ $

P.S:
rustc hello world compile time is 38 times slower that gcc, rust executable is 292 times bigger than C executable ...

Code: Select all

pi@raspberrypi3BplusX:~ $ time /home/pi/.rustup/toolchains/nightly-armv7-unknown-linux-gnueabihf/bin/rustc hello.rs 

real	0m10.985s
user	0m2.108s
sys	0m0.369s
pi@raspberrypi3BplusX:~ $ ls -l hello
-rwxr-xr-x 1 pi pi 2386156 Dec 26 23:59 hello
pi@raspberrypi3BplusX:~ $ 

Code: Select all

pi@raspberrypi3BplusX:~ $ time gcc hello.c

real	0m0.286s
user	0m0.245s
sys	0m0.040s
pi@raspberrypi3BplusX:~ $ ls -l a.out 
-rwxr-xr-x 1 pi pi 8148 Dec 27 00:02 a.out
pi@raspberrypi3BplusX:~ $ 

[scruss]

... rust executable is 292 times bigger than C executable ...

But is statically linked, IIRC. Like golang, rust does its best to avoid DLL Hell.

[HermannSW]

OK, but C static hello world is still more than 4 times smaller, and compiles 25 times faster than rustc:

Code: Select all

pi@raspberrypi3BplusX:~ $ time gcc -static hello.c

real	0m0.435s
user	0m0.348s
sys	0m0.084s
pi@raspberrypi3BplusX:~ $ ls -l a.out
-rwxr-xr-x 1 pi pi 569264 Dec 27 00:06 a.out
pi@raspberrypi3BplusX:~ $ ./a.out 
Hello World!
pi@raspberrypi3BplusX:~ $

Of course there are other advantages of Rust over C -- but Raspbian is definitely not a platform tested since stable rustc just hangs.

[hippy]

OK, but C static hello world is still more than 4 times smaller, and compiles 25 times faster than rustc:

I can't help with whatever issue you have but, having not used rustc before, I installed it on my Pi3B (non-plus) using 'sudo apt-get install rustc', used your hello.rs, and ...

Code: Select all

pi@Pi3B:~$ rustc --version
rustc 1.24.1 (f2dda7fd7 2018-08-16)
pi@Pi3B:~$ time rustc hello.rs
real    0m2.835s
user    0m2.580s
sys     0m0.254s
pi@Pi3B:~$ ls -l hello
-rwxr-xr-x 1 pi pi 266840 Dec 27 12:27 hello
pi@Pi3B:~$pi@Pi3B:~$ ./hello
Hello World!
pi@Pi3B:~$

That probably isn't all of what you personally need but I thought the numbers might be useful or interesting to see.

[HermannSW]

Thanks for that information.
I installed rustc now as you did via apt-get install, and not by the official method from link in initial posting of this thread.
I get same results as you (compile time is 2.313s on Pi 3B+).
The new executable size is now half of that of the static C binary, all good with this version of rustc.

Not sure what else the nightly rustc generates into the binary, maybe its just the newer version that blew up binary size:

Code: Select all

pi@raspberrypi3BplusX:~ $ /home/pi/.rustup/toolchains/nightly-armv7-unknown-linux-gnueabihf/bin/rustc --version
rustc 1.33.0-nightly (adbfec229 2018-12-17)
pi@raspberrypi3BplusX:~ $ 

[hippy]

Code: Select all

real	0m10.985s
user	0m2.108s
sys	0m0.369s

That 'real' is significantly longer than 'user' so I'm wondering if your nightly builds could be trying to fetch something from a server somewhere, trying to connect to a service which doesn't exist, is hanging while waiting for a timeout ?

[paddyg]

@HermannSW I tried `rustup update` on my RPi to latest (stable; 1.31 '2018' version) Yesterday, after noticing this thread, and got various errors with failure to complete. When I tried it again today it all went through OK. So I think whatever problems have been fixed (though no post on the forum you linked to). Following the `standard` route using rustup, cargo etc might make development easier than using rustc. Rust will take longer to compile than C and will produce bigger applications but it will probably be worth it!

[HermannSW]

Sorry, I forgot to update here after I got a lot help on rust forum and finaly was able to figure out the issue.
https://users.rust-lang.org/t/why-does- ... h/22760/20

Summary:

latest stable rustc hangs on Raspbian
latest nightly rustc is good on Raspbian