Re: [bootstrappable] prototyping the full source bootstrap path

[ludo@gnu.org (Ludovic Courtès)]

Heya Jan,

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> Now that MesCC starts to build TinyCC that starts to pass a large set of
> the mescc C tests, it's time to get walking the bootstrap path.

Woohoo!

> Attached*) is my initial attempt for the full source bootstrap path in
> GuixSD; to try it, do
>
>     ./pre-inst-env guix build mes-boot
>     ...
>     /gnu/store/lj7h0s33qghgk4zw2nb133riz7xhara9-mes-boot-0.11-0.948dd79/bin/mes --help
>
> The starting point is Jeremiah Orian's stage0 self hosting hex
> assembler.  The binary seed of our bootstrap is made explicit in an
> additional source download: stage0-seed (of ~400 bytes).  This binary
> that is identical with it's ASCII source can be considered "source".
>
> There are still many gaps in our full source bootstrap path to-be, I
> "filled" these by adding additional binary seeds: mescc-tools-seed and
> mes-seed.  We are working to remove these, that will take some time.
>
> The mes-boot package needs a lot more work and tinycc-boot, gcc-boot
> packages are still missing.

Sounds like a good start.

So the next steps in the dependency graph are:

  mes-boot -> mescc -> tinycc -> gcc@4.7 -> gcc

Do I get this right?

Also, AIUI, stage0 is i386-specific.  Thoughts on how we can eventually
support the other architectures Guix works on?

Thank you, and congrats on this milestone!

Ludo’.