risc-v is obv cool but i don't have any hardware for it
Discussion
Loading...
Post
hell fucking YES we are adding support for x86 cygwin. ran emacs in that shit when i interned at microsoft. deep behind enemy lines
of course the fucked up little config format says hey you know what makes perfect sense to add along with specifications of what output formats to build for? that's right!! host-specific binary paths
oh you're building our programming language on your own computer instead of rented software on rented hardware? that's so cute!!! i love retro stuff like that
you cannot be fucking serious https://forge.rust-lang.org/infra/other-installation-methods.html#source-code this link is hidden in the middle of the bootstrap.example.toml. not mentioned anywhere in the fucking INSTALL.md that negs you about building from source. no they actually have fucking source tarballs too. jesus fucking christ they're up to date links too
for context, the bootstrap.example.toml file is >1000 lines of commented text
they also provide gpg signatures the way everyone else does (except pypi because they had a corporate offering to sell)
~79 more replies (not shown)
the file ordering in the tar file is all fucked up because clearly some smartass wanted to generate it with 1337 h4XX0r parallelism. or alternatively it's just fucked up for no reason
just including all the test data from the lzma-sys crate. yeah i agree bandwidth and disk space are free and i need those to build your language
this is actually the crux of the wheel proposal i'm making btw and it's why i haven't done it yet bc zstd alone is missing most of the savings vs classifying output files from the build system
oh my god that's 273M with xz compression. zero effort. negative effort
literally so close to getting it
# Set the bootstrap/download cache path. It is useful when building rust
# repeatedly in a CI environment.
#build.bootstrap-cache-path = /path/to/shared/cache
what if we had a method to cache outputs that are shared across invocations of the bootstrapping process. what if?
now it turns out there's a secret flag that completely changes all of the build requirements
# Use the optimized LLVM C intrinsics for `compiler_builtins`, rather than Rust intrinsics.
# Choosing true requires the LLVM submodule to be managed by bootstrap (i.e. not external)
# so that `compiler-rt` sources are available.
now i've heard there was a secret flag
that toml displayed for the runtime source
but you don't really care for C now, do you
# Setting this to a path removes the requirement for a C toolchain, but requires setting the
# path to an existing library containing the builtins library from LLVM's compiler-rt.
literally just a fucking riddle. this is the canonical "schema" for building rustc
important followup
# Setting this to `false` generates slower code, but removes the requirement for a C toolchain in
# order to run `x check`.
this is a riddle
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled