#rustup

2025-05-05

We’re hopefully making new #rustup releases more often so people won’t mistake us for maintaining “done software” 😶
blog.rust-lang.org/2025/05/05/

2025-05-03

@adanskana AFAIR, this is the reason #GNAT is not distributed through #Homebrew either.

Perhaps instead of GNAT, distributions could package #Alire ? [1] It can be used to obtain open source #AdaLang / #SPARKLang toolchains (including #FSF GNAT licensed under #GPL with GCC RLE) similarly to how #RustLang toolchain can be obtained with #Rustup . Alire is like a mix of Rustup and #Cargo, but for #Ada.

[1] alire.ada.dev

Michał Fitamichalfita
2025-04-09

@2ndNatureDev doc.rust-lang.org/rustc/platfo

may not provide binaries for this target and building this target requires SDK. The SDK may be on proprietary license and distribution of the binary could be forbidden (I haven't checked).

Michal Vyskočilvyskocilm@witter.cz
2025-03-23

The fact #rustup does handle update of a clippy is neat.

#rust

Leniwcowaty :fedora: :kdenew:leniwcowaty@fosstodon.org
2025-03-20

Fun #activities from last night:
Spending 4 hours trying to come up with a way to install #Alacritty on #Aurora #Linux without layering packages.
I ended up installing #rustup from #homebrew, using rustup to setup #cargo and then using cargo to install Alacritty. And I had to make .desktop file myself.
Only caveat - no way to include updating cargo and crates in "ujust update" (or I'm not smart enough). So after updating I have to manually run "rustup update" and "cargo install alacritty"

2025-02-26

With #rustup, we can view the #Rust #documentation in our browser :firefox: which is very helpful.

The docs are located at "${HOME}/.rustup/toolchains/"${ToolChain}/share/doc/rust/html/"

If your browser can't access that location (for instance due to confinement rules), you can spin up a quick http server

:python: 🌐 python3 -m http.server --directory "${HOME}/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/share/doc/rust/html/" 9005

Or, you could spin up an NGINX server block, if you're so inclined.

Here's mine running in #Firefox :firefox: on #KUbuntu :kubuntu: (#ubuntu :ubuntu: )

#rustlang #rustdoc

Rust documentation hosted by a python webserver, displayed in Firefox
2024-10-25
Since I guess Google knows Rust better than me I guess I'm doing the state of art with custom target JSON-files, i.e. deploying them to a random directory in the project directory :-)

I kind of hoped that there would be a place (let's say .cargo/targets or similar) under the project that gets automatically recognized by the tooling. Then you could just put that to rust-toolchain.xml like any other target.

https://security.googleblog.com/2024/09/deploying-rust-in-existing-firmware.html

#cargo #rust #rustup
ShadowKyogreShadowKyogre
2024-10-19

Okay, I got my coding tools sorted out on both my half and my half now.

So far that consists of (for vers), , and (for vers).

...I'm *not* sure if I should look into a version manager for or just yet, since that affects the web dev stuff I do on the side.

David Cantrell 🏏DrHyde@fosstodon.org
2024-06-14

Just upgraded to #FreeBSD 14.1 on my dev and CPAN-testing VMs. It's a bit odd that I had to reinstall everything that I'd installed from packages (on the first attempt I missed that step in the instructions and NOTHING worked because libraries changed, yay for just rolling back the entire VM), but things I'd built myself from source continue to Just Work. #rustup shat the bed on one machine, no idea why and can't be arsed to debug, so uninstalled/reinstalled and all looks good.

Todd A. Jacobs | Rubyisttodd_a_jacobs@ruby.social
2024-04-26

So, yup. The #rustc installed by #homebrew in bottle 1.77.2 won't work right; something's broken in the librustc_driver dylib file. Luckily, you can still build #RubyLang with #YJIT just fine using #rustup instead.

```fish
~> brew install rustup-init &&
source ~/.cargo/env.fish &&
ruby --yjit --version
ruby 3.3.1 (2024-04-23 revision c56cd86388) +YJIT [arm64-darwin23]
```

Todd A. Jacobs | Rubyisttodd_a_jacobs@ruby.social
2024-04-26

I'm currently trying to get #RubyLang 3.3.1 to compile with `--enable-yjit` set. For some reason, the newest #CRuby version won't build on Sonoma because #RustLang is missing some include or header required for the latest #YJIT to be built.

It seems to be a problem with #rustc. I'm trying with #rustup instead, and will see how that goes.

2024-01-15

Why is it suddenly getting so popular to install linux packages by "Just download this executable file and run it"?! `curl | sh` should be banned. AppImage and Flatpak are not much better. Isn't this how MS Windows became full of viruses? Users just clicking random executables from internet as a norm? Looking at you, #rust, #rustup.

atareao 🦀🐍🐋🐧atareao
2023-11-21

Instalación, configuración y personalización de Rust en Linux
En este vídeo te muestro como instalar, configurar y personalizar en para que le saques el máximo provecho. De la misma forma, también te explico como utilizar herramientas como y que te van a permitir funcionar con este increíble lenguaje de programación.

🌐 Aquí lo puedes encontrar todo 👉 atareao.es
✈️ Telegram (el grupo) 👉 https:/

youtube.com/watch?v=KykHyCo0rJE

2023-11-16

Installing #rustup:

alias rustup="curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | bash -s --"

E.g.

rustup --no-modify-path

Just though that good to write this up since I see some distributions packaging rustup, which makes no sense (for #rustc and #cargo it does for obvious reasons).

It is also totally safe to run rustup this way kudos to the amazing #TLS 1.2.

#rustlang

2023-10-13

In the Rust ecosystem, rustup is unique and fantastic.

It's the official way of installing Rust on all platforms.

It enables having delivery "channels" (nightly, stable…) that are updated regularly.

#RustLang #EuroRust #EuroRust23 #rustup

Jay Lanaganjloc0
2023-07-05

Ended up going with . So now we’re back to building on x86 and attempting to verify my scripts along the way. I wonder if I’ll get to the desktop tonight.

Aniket Das❄️aniketofficial
2023-04-18

# Rust Trademark Policy Draft Revision – Next Steps

Here’s what’s next with the Rust Trademark Policy revision process as we review your feedback on the initial draft and work to address it in a new version.

Read the full article at :-
foundation.rust-lang.org/news/

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst