home.social

#bootstrappablebuilds — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bootstrappablebuilds, aggregated by home.social.

  1. @nixos_org @nzbr

    While we're on the topic: work on minimal-bootstrap in #nixpkgs has actually been picked up again since this thesis was written (October 2025).

    Not only that but, as of a few hours ago, the PR implementing the last step of hooking it up to become the actual bootstrap stdenv in Nixpkgs has been merged!

    github.com/NixOS/nixpkgs/pull/

    #fullsourcebootstrap #reproduciblebuilds #stage0 #minimalbootstrap #bootstrappablebuilds

  2. @nixos_org @nzbr

    While we're on the topic: work on minimal-bootstrap in #nixpkgs has actually been picked up again since this thesis was written (October 2025).

    Not only that but, as of a few hours ago, the PR implementing the last step of hooking it up to become the actual bootstrap stdenv in Nixpkgs has been merged!

    github.com/NixOS/nixpkgs/pull/

    #fullsourcebootstrap #reproduciblebuilds #stage0 #minimalbootstrap #bootstrappablebuilds

  3. @nixos_org @nzbr

    While we're on the topic: work on minimal-bootstrap in #nixpkgs has actually been picked up again since this thesis was written (October 2025).

    Not only that but, as of a few hours ago, the PR implementing the last step of hooking it up to become the actual bootstrap stdenv in Nixpkgs has been merged!

    github.com/NixOS/nixpkgs/pull/

    #fullsourcebootstrap #reproduciblebuilds #stage0 #minimalbootstrap #bootstrappablebuilds

  4. @nixos_org @nzbr

    While we're on the topic: work on minimal-bootstrap in #nixpkgs has actually been picked up again since this thesis was written (October 2025).

    Not only that but, as of a few hours ago, the PR implementing the last step of hooking it up to become the actual bootstrap stdenv in Nixpkgs has been merged!

    github.com/NixOS/nixpkgs/pull/

    #fullsourcebootstrap #reproduciblebuilds #stage0 #minimalbootstrap #bootstrappablebuilds

  5. @nixos_org @nzbr

    While we're on the topic: work on minimal-bootstrap in #nixpkgs has actually been picked up again since this thesis was written (October 2025).

    Not only that but, as of a few hours ago, the PR implementing the last step of hooking it up to become the actual bootstrap stdenv in Nixpkgs has been merged!

    github.com/NixOS/nixpkgs/pull/

    #fullsourcebootstrap #reproduciblebuilds #stage0 #minimalbootstrap #bootstrappablebuilds

  6. @filippo Meanwhile, bootstrapping a current OpenJDK involves compiling multiple ancient packages (each with its own set of outdated dependencies, of course) and then going up all the way from Java 7, version by version.

    @stikonas has described this tedious process and developed some ebuilds for Gentoo here: git.stikonas.eu/andrius/gentoo

    This also applies to Rust in a way, but at least it's not as bad there – not yet, as the old versions might eventually succumb to bitrot, too.

    Please, dear programming language community, can we do better at this? For resilience, for reproducibility, for reliability, for portability and for preservation?

    #bootstrappablebuilds #bootstrapping #reproduciblebuilds #trustingtrust #gentoo #openjdk #rust

  7. @filippo Meanwhile, bootstrapping a current OpenJDK involves compiling multiple ancient packages (each with its own set of outdated dependencies, of course) and then going up all the way from Java 7, version by version.

    @stikonas has described this tedious process and developed some ebuilds for Gentoo here: git.stikonas.eu/andrius/gentoo

    This also applies to Rust in a way, but at least it's not as bad there – not yet, as the old versions might eventually succumb to bitrot, too.

    Please, dear programming language community, can we do better at this? For resilience, for reproducibility, for reliability, for portability and for preservation?

    #bootstrappablebuilds #bootstrapping #reproduciblebuilds #trustingtrust #gentoo #openjdk #rust

  8. @filippo Meanwhile, bootstrapping a current OpenJDK involves compiling multiple ancient packages (each with its own set of outdated dependencies, of course) and then going up all the way from Java 7, version by version.

    @stikonas has described this tedious process and developed some ebuilds for Gentoo here: git.stikonas.eu/andrius/gentoo

    This also applies to Rust in a way, but at least it's not as bad there – not yet, as the old versions might eventually succumb to bitrot, too.

    Please, dear programming language community, can we do better at this? For resilience, for reproducibility, for reliability, for portability and for preservation?

    #bootstrappablebuilds #bootstrapping #reproduciblebuilds #trustingtrust #gentoo #openjdk #rust

  9. @filippo Meanwhile, bootstrapping a current OpenJDK involves compiling multiple ancient packages (each with its own set of outdated dependencies, of course) and then going up all the way from Java 7, version by version.

    @stikonas has described this tedious process and developed some ebuilds for Gentoo here: git.stikonas.eu/andrius/gentoo

    This also applies to Rust in a way, but at least it's not as bad there – not yet, as the old versions might eventually succumb to bitrot, too.

    Please, dear programming language community, can we do better at this? For resilience, for reproducibility, for reliability, for portability and for preservation?

    #bootstrappablebuilds #bootstrapping #reproduciblebuilds #trustingtrust #gentoo #openjdk #rust

  10. @filippo Meanwhile, bootstrapping a current OpenJDK involves compiling multiple ancient packages (each with its own set of outdated dependencies, of course) and then going up all the way from Java 7, version by version.

    @stikonas has described this tedious process and developed some ebuilds for Gentoo here: git.stikonas.eu/andrius/gentoo

    This also applies to Rust in a way, but at least it's not as bad there – not yet, as the old versions might eventually succumb to bitrot, too.

    Please, dear programming language community, can we do better at this? For resilience, for reproducibility, for reliability, for portability and for preservation?

    #bootstrappablebuilds #bootstrapping #reproduciblebuilds #trustingtrust #gentoo #openjdk #rust

  11. Edit: Added &c=my-comment to the URL,
    please like my comment, or otherwise help me to reach LaurieWired? Boost=❤️ #askfedi

    @regtur @reproducible_builds @guix @ekaitz_zarraga
    @nlnet
    @fsf
    @fsfe
    @gnutools
    Seems #fedi didn't do their thing just yet, so I logged into the Evil Empire and added a comment. Not sure if that will do any good, tho. I guess maybe one or two of you who read this, and still have a Google account, could like my comment, but there are already comments with > 3K likes, so yeah.

    Also, no idea how to reach them; they're talking about trust, and then only seem to on Big Tech platforms like TPPKAB (the platform previously known as birdsite), instagram, etc.

    <youtube.com/watch?v=Fu3laL5VYd>
    #bootstrappablebuilds #guix #gnu #reproducibleBuilds #supplyChainSecurity #trustingTrust

  12. Edit: Added &c=my-comment to the URL,
    please like my comment, or otherwise help me to reach LaurieWired? Boost=❤️ #askfedi

    @regtur @reproducible_builds @guix @ekaitz_zarraga
    @nlnet
    @fsf
    @fsfe
    @gnutools
    Seems #fedi didn't do their thing just yet, so I logged into the Evil Empire and added a comment. Not sure if that will do any good, tho. I guess maybe one or two of you who read this, and still have a Google account, could like my comment, but there are already comments with > 3K likes, so yeah.

    Also, no idea how to reach them; they're talking about trust, and then only seem to on Big Tech platforms like TPPKAB (the platform previously known as birdsite), instagram, etc.

    <youtube.com/watch?v=Fu3laL5VYd>
    #bootstrappablebuilds #guix #gnu #reproducibleBuilds #supplyChainSecurity #trustingTrust

  13. Edit: Added &c=my-comment to the URL,
    please like my comment, or otherwise help me to reach LaurieWired? Boost=❤️ #askfedi

    @regtur @reproducible_builds @guix @ekaitz_zarraga
    @nlnet
    @fsf
    @fsfe
    @gnutools
    Seems #fedi didn't do their thing just yet, so I logged into the Evil Empire and added a comment. Not sure if that will do any good, tho. I guess maybe one or two of you who read this, and still have a Google account, could like my comment, but there are already comments with > 3K likes, so yeah.

    Also, no idea how to reach them; they're talking about trust, and then only seem to on Big Tech platforms like TPPKAB (the platform previously known as birdsite), instagram, etc.

    <youtube.com/watch?v=Fu3laL5VYd>
    #bootstrappablebuilds #guix #gnu #reproducibleBuilds #supplyChainSecurity #trustingTrust

  14. Edit: Added &c=my-comment to the URL,
    please like my comment, or otherwise help me to reach LaurieWired? Boost=❤️ #askfedi

    @regtur @reproducible_builds @guix @ekaitz_zarraga
    @nlnet
    @fsf
    @fsfe
    @gnutools
    Seems #fedi didn't do their thing just yet, so I logged into the Evil Empire and added a comment. Not sure if that will do any good, tho. I guess maybe one or two of you who read this, and still have a Google account, could like my comment, but there are already comments with > 3K likes, so yeah.

    Also, no idea how to reach them; they're talking about trust, and then only seem to on Big Tech platforms like TPPKAB (the platform previously known as birdsite), instagram, etc.

    <youtube.com/watch?v=Fu3laL5VYd>
    #bootstrappablebuilds #guix #gnu #reproducibleBuilds #supplyChainSecurity #trustingTrust

  15. Edit: Added &c=my-comment to the URL,
    please like my comment, or otherwise help me to reach LaurieWired? Boost=❤️ #askfedi

    @regtur @reproducible_builds @guix @ekaitz_zarraga
    @nlnet
    @fsf
    @fsfe
    @gnutools
    Seems #fedi didn't do their thing just yet, so I logged into the Evil Empire and added a comment. Not sure if that will do any good, tho. I guess maybe one or two of you who read this, and still have a Google account, could like my comment, but there are already comments with > 3K likes, so yeah.

    Also, no idea how to reach them; they're talking about trust, and then only seem to on Big Tech platforms like TPPKAB (the platform previously known as birdsite), instagram, etc.

    <youtube.com/watch?v=Fu3laL5VYd>
    #bootstrappablebuilds #guix #gnu #reproducibleBuilds #supplyChainSecurity #trustingTrust

  16. #GNU Mes 0.27.1 released: A bug-fix release that supports

    * development build with gcc-14
    * building with M2-Planet 1.12.0
    * building on x86-linux with M2-Planet 1.13.0
    * building bootstrappable-tcc using 1.00.02 <= NYACC <= 2.02.2

    <lists.gnu.org/archive/html/inf>

    Thanks to @ekaitz_zarraga and @stikonas!

    #GnuMes
    #bootstrappable
    #BootstrappableBuilds
    #ReproducibleBuilds
    @reproducible_builds
    @fsf
    @fsfe
    @gnutools
    @nlnet

  17. #GNU Mes 0.27.1 released: A bug-fix release that supports

    * development build with gcc-14
    * building with M2-Planet 1.12.0
    * building on x86-linux with M2-Planet 1.13.0
    * building bootstrappable-tcc using 1.00.02 <= NYACC <= 2.02.2

    <lists.gnu.org/archive/html/inf>

    Thanks to @ekaitz_zarraga and @stikonas!

    #GnuMes
    #bootstrappable
    #BootstrappableBuilds
    #ReproducibleBuilds
    @reproducible_builds
    @fsf
    @fsfe
    @gnutools
    @nlnet

  18. #GNU Mes 0.27.1 released: A bug-fix release that supports

    * development build with gcc-14
    * building with M2-Planet 1.12.0
    * building on x86-linux with M2-Planet 1.13.0
    * building bootstrappable-tcc using 1.00.02 <= NYACC <= 2.02.2

    <lists.gnu.org/archive/html/inf>

    Thanks to @ekaitz_zarraga and @stikonas!

    #GnuMes
    #bootstrappable
    #BootstrappableBuilds
    #ReproducibleBuilds
    @reproducible_builds
    @fsf
    @fsfe
    @gnutools
    @nlnet

  19. #GNU Mes 0.27.1 released: A bug-fix release that supports

    * development build with gcc-14
    * building with M2-Planet 1.12.0
    * building on x86-linux with M2-Planet 1.13.0
    * building bootstrappable-tcc using 1.00.02 <= NYACC <= 2.02.2

    <lists.gnu.org/archive/html/inf>

    Thanks to @ekaitz_zarraga and @stikonas!

    #GnuMes
    #bootstrappable
    #BootstrappableBuilds
    #ReproducibleBuilds
    @reproducible_builds
    @fsf
    @fsfe
    @gnutools
    @nlnet

  20. #GNU Mes 0.27.1 released: A bug-fix release that supports

    * development build with gcc-14
    * building with M2-Planet 1.12.0
    * building on x86-linux with M2-Planet 1.13.0
    * building bootstrappable-tcc using 1.00.02 <= NYACC <= 2.02.2

    <lists.gnu.org/archive/html/inf>

    Thanks to @ekaitz_zarraga and @stikonas!

    #GnuMes
    #bootstrappable
    #BootstrappableBuilds
    #ReproducibleBuilds
    @reproducible_builds
    @fsf
    @fsfe
    @gnutools
    @nlnet

  21. I was just reviewing the new x86 hex0 bootstrap seed: github.com/oriansj/stage0-posi. Big thanks to Noah Goldstein for making it smaller.

    Now it is only 190 bytes. Excluding ELF header that's only 106 bytes of code.

    For a couple of years hex0 binary was 256 bytes and before that hex0 was 357 bytes (this is the number that is still mentioned in guix.gnu.org/manual/devel/en/h).

  22. I was just reviewing the new x86 hex0 bootstrap seed: github.com/oriansj/stage0-posi. Big thanks to Noah Goldstein for making it smaller.

    Now it is only 190 bytes. Excluding ELF header that's only 106 bytes of code.

    For a couple of years hex0 binary was 256 bytes and before that hex0 was 357 bytes (this is the number that is still mentioned in guix.gnu.org/manual/devel/en/h).

    #bootstrappableBuilds #stage0

  23. I was just reviewing the new x86 hex0 bootstrap seed: github.com/oriansj/stage0-posi. Big thanks to Noah Goldstein for making it smaller.

    Now it is only 190 bytes. Excluding ELF header that's only 106 bytes of code.

    For a couple of years hex0 binary was 256 bytes and before that hex0 was 357 bytes (this is the number that is still mentioned in guix.gnu.org/manual/devel/en/h).

    #bootstrappableBuilds #stage0

  24. @filip The current project is focused on running the compiler in a Scheme implementation, and generating native code with a C compiler.

    The bootstrapping story is really a question of "how much Scheme" and "how much C". I'd love for Pre-Scheme to run on GNU Mes, but that hasn't been investigated yet. I'm in touch with folks in the bootstrapping community who are experts in minimal C compilers, and intend to do a detailed analysis of compatibility at some point. Early diagnosis is that Pre-Scheme isn't very demanding of a C compiler and targeting minimal compilers should be possible.

    Beyond that, there's the possibility for adding new backends to the Pre-Scheme compiler. The original compiler described in "Compilation By Program Transformation" emitted m68k assembly. The paper "A Tractable Native-Code Scheme System" describes re-purposing the compiler as a bytecode optimizer, which involved writing a backend to emit Scheme 48 bytecode. I also have colleagues who are very interested in the possibility of a WebAssembly backend.

    prescheme.org/references.html

    #prescheme #bootstrappablebuilds

  25. @filip The current project is focused on running the compiler in a Scheme implementation, and generating native code with a C compiler.

    The bootstrapping story is really a question of "how much Scheme" and "how much C". I'd love for Pre-Scheme to run on GNU Mes, but that hasn't been investigated yet. I'm in touch with folks in the bootstrapping community who are experts in minimal C compilers, and intend to do a detailed analysis of compatibility at some point. Early diagnosis is that Pre-Scheme isn't very demanding of a C compiler and targeting minimal compilers should be possible.

    Beyond that, there's the possibility for adding new backends to the Pre-Scheme compiler. The original compiler described in "Compilation By Program Transformation" emitted m68k assembly. The paper "A Tractable Native-Code Scheme System" describes re-purposing the compiler as a bytecode optimizer, which involved writing a backend to emit Scheme 48 bytecode. I also have colleagues who are very interested in the possibility of a WebAssembly backend.

    prescheme.org/references.html

    #prescheme #bootstrappablebuilds

  26. @filip The current project is focused on running the compiler in a Scheme implementation, and generating native code with a C compiler.

    The bootstrapping story is really a question of "how much Scheme" and "how much C". I'd love for Pre-Scheme to run on GNU Mes, but that hasn't been investigated yet. I'm in touch with folks in the bootstrapping community who are experts in minimal C compilers, and intend to do a detailed analysis of compatibility at some point. Early diagnosis is that Pre-Scheme isn't very demanding of a C compiler and targeting minimal compilers should be possible.

    Beyond that, there's the possibility for adding new backends to the Pre-Scheme compiler. The original compiler described in "Compilation By Program Transformation" emitted m68k assembly. The paper "A Tractable Native-Code Scheme System" describes re-purposing the compiler as a bytecode optimizer, which involved writing a backend to emit Scheme 48 bytecode. I also have colleagues who are very interested in the possibility of a WebAssembly backend.

    prescheme.org/references.html

    #prescheme #bootstrappablebuilds

  27. @filip The current project is focused on running the compiler in a Scheme implementation, and generating native code with a C compiler.

    The bootstrapping story is really a question of "how much Scheme" and "how much C". I'd love for Pre-Scheme to run on GNU Mes, but that hasn't been investigated yet. I'm in touch with folks in the bootstrapping community who are experts in minimal C compilers, and intend to do a detailed analysis of compatibility at some point. Early diagnosis is that Pre-Scheme isn't very demanding of a C compiler and targeting minimal compilers should be possible.

    Beyond that, there's the possibility for adding new backends to the Pre-Scheme compiler. The original compiler described in "Compilation By Program Transformation" emitted m68k assembly. The paper "A Tractable Native-Code Scheme System" describes re-purposing the compiler as a bytecode optimizer, which involved writing a backend to emit Scheme 48 bytecode. I also have colleagues who are very interested in the possibility of a WebAssembly backend.

    prescheme.org/references.html

    #prescheme #bootstrappablebuilds

  28. @filip The current project is focused on running the compiler in a Scheme implementation, and generating native code with a C compiler.

    The bootstrapping story is really a question of "how much Scheme" and "how much C". I'd love for Pre-Scheme to run on GNU Mes, but that hasn't been investigated yet. I'm in touch with folks in the bootstrapping community who are experts in minimal C compilers, and intend to do a detailed analysis of compatibility at some point. Early diagnosis is that Pre-Scheme isn't very demanding of a C compiler and targeting minimal compilers should be possible.

    Beyond that, there's the possibility for adding new backends to the Pre-Scheme compiler. The original compiler described in "Compilation By Program Transformation" emitted m68k assembly. The paper "A Tractable Native-Code Scheme System" describes re-purposing the compiler as a bytecode optimizer, which involved writing a backend to emit Scheme 48 bytecode. I also have colleagues who are very interested in the possibility of a WebAssembly backend.

    prescheme.org/references.html

    #prescheme #bootstrappablebuilds

  29. @harrysintonen @vegard These days we also have that prevent this kind of attack (at least at the software level).

  30. @harrysintonen @vegard These days we also have #BootstrappableBuilds that prevent this kind of attack (at least at the software level).

  31. @harrysintonen @vegard These days we also have #BootstrappableBuilds that prevent this kind of attack (at least at the software level).

  32. @harrysintonen @vegard These days we also have #BootstrappableBuilds that prevent this kind of attack (at least at the software level).

  33. @harrysintonen @vegard These days we also have #BootstrappableBuilds that prevent this kind of attack (at least at the software level).