|
|
Subscribe / Log in / New account

Woodruff: Weird architectures weren't supported to begin with

Woodruff: Weird architectures weren't supported to begin with

Posted Mar 2, 2021 17:50 UTC (Tue) by mathstuf (subscriber, #69389)
In reply to: Woodruff: Weird architectures weren't supported to begin with by rweikusat2
Parent article: Woodruff: Weird architectures weren't supported to begin with

Why did you not download the precompiled binaries (via rustup or whatever) for Ubuntu? Also, the Rust repo has the LLVM it works with in the repository (via a submodule). Given the patches they've had to apply over time, using an external LLVM probably wouldn't work out *that* well anyways.

For the Yocto bit, there is a TOML file which can describe the target rather than patching the compiler, but agreeing with autoconf does sound like something might need to be tweaked there. I think there are those who are doing embedded development with Rust; asking on those channels for guidance would likely be how I would have handled it. But, I haven't needed to do anything like that, so I don't have much experience to offer here.


to post comments

Woodruff: Weird architectures weren't supported to begin with

Posted Mar 2, 2021 18:13 UTC (Tue) by rweikusat2 (subscriber, #117920) [Link] (1 responses)

Why does answering such a question invariably lead to someone answering questions nobody ever asked?

Ubuntu has a rust package. Please ask the maintainer why he doesn't just tell its users to download something from the internet instead.

Assumptions hard-code in the build system can't be "overridden" via configuration files. That's - BTW - the very meaning of "hard-coded".

Woodruff: Weird architectures weren't supported to begin with

Posted Mar 2, 2021 18:28 UTC (Tue) by mathstuf (subscriber, #69389) [Link]

Well, if you're looking to compile it yourself, the Ubuntu package was apparently not suitable. Was it suitable? Then why were you looking to compile it yourself?

> Assumptions hard-code in the build system can't be "overridden" via configuration files. That's - BTW - the very meaning of "hard-coded".

Like I said, I've not dealt with embedded details, but I have seen that new targets can be described via TOML files (up to LLVM configurability). But yes, if you're fighting internal logic, you're stuck with patching.

Woodruff: Weird architectures weren't supported to begin with

Posted Mar 7, 2021 23:01 UTC (Sun) by nix (subscriber, #2304) [Link]

> Also, the Rust repo has the LLVM it works with in the repository (via a submodule). Given the patches they've had to apply over time, using an external LLVM probably wouldn't work out *that* well anyways.

This has improved greatly of late: since about LLVM 10, a separately-compiled upstream LLVM works well enough. (IIRC, there are hardly any patches left in Rust's not-a-fork of LLVM any more.)


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds