Oreboot similar to Libreboot is focused on targeting "truly open systems" as Coreboot without binary blobs.
Announcement
Collapse
No announcement yet.
Oreboot Is Taking Shape As Rust'ed, Purely Open-Source Focused Coreboot
Collapse
X
-
Originally posted by jjkk View Post
Requires compiler which can not be built from source code without downloading a binary blob.Last edited by ssokolow; 03 September 2019, 06:13 PM.
- Likes 1
Comment
-
Code:curl https://sh.rustup.rs -sSf | sh
- Likes 2
Comment
-
-
Originally posted by jjkk View PostRequires compiler which can not be built from source code without downloading a binary blob.
Are you fucking serious?
- Likes 3
Comment
-
Originally posted by jjkk View PostIt seems you have never tried the method you are suggesting. Because it is utterly broken. If that was possible why would the one and only official method to install Rust was so ridiculous and laughable?
Code:curl https://sh.rustup.rs -sSf | sh
Bootstrapping is not intended as an official method to install it, any more than expecting building GCC with some random compiler like TCC to be an official supported method of install. If you want to bootstrap a self-hosting compiler, there's an implicit expectation that you're skilled enough to write your own instructions as you go.
mrustc's purpose is to prove that the official binaries are safe by producing bit-for-bit identical replicas through a laborious but much more auditable process.
If it's the "running arbitrary shell scripts" part you have a problem with, that's what the Other Installation Methods page is for. (Though you won't see me arguing if you complain that the current incarnation of the site is an iOS-ishly confusing "determined to be simpler than is actually possible" mess.)
- Likes 2
Comment
-
Originally posted by ssokolow View Post
For the same reason that GCC doesn't provide a tutorial on how to bootstrap GCC from a non-C++ compiler... or, as far as a quick google shows, from a non-GCC C++ compiler. (And, yes, GCC stopped being pure C a few years ago as was mentioned here on Phoronix.)
Clean bootstrapping current gcc has come a pain in the ass its tinyc to GCC 2.95.0 to gcc 4.7 then to current. Yes this bootstrap path is required when you have a clean platform with no binaries.
Its not like it really was impossible to write the core of the compiler in C++ yet still boot strap with C just no one really wanted to.
ssokolow gcc boot strapping build the xgcc is built then the xgcc rebuild the code again. So its currently 7 builds to clean boot strap gcc due to the change to c++.
Yes a C++ to C converter + tcc could possible allow building the current xgcc so making 3 builds to boot strap.
Really needing to clean bootstrap with audited code current gcc is a bastard.
Comment
-
Originally posted by oiaohm View Post
https://bootstrappable.org/projects/mes.html Many project maintain the tutorial howto bootstrap current gcc from non C++ compiler
Clean bootstrapping current gcc has come a pain in the ass its tinyc to GCC 2.95.0 to gcc 4.7 then to current. Yes this bootstrap path is required when you have a clean platform with no binaries.
Its not like it really was impossible to write the core of the compiler in C++ yet still boot strap with C just no one really wanted to.
ssokolow gcc boot strapping build the xgcc is built then the xgcc rebuild the code again. So its currently 7 builds to clean boot strap gcc due to the change to c++.
Yes a C++ to C converter + tcc could possible allow building the current xgcc so making 3 builds to boot strap.
Really needing to clean bootstrap with audited code current gcc is a bastard.
- Likes 1
Comment
Comment