all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: bootstrappable@freelists.org
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [bootstrappable] Re: prototyping the full source bootstrap path
Date: Mon, 20 Nov 2017 20:22:10 +0100	[thread overview]
Message-ID: <CAE4v=pgeD1KouSMiEOfHWOQOSfYUbL673Vhj9uCoNDSSLxYNbQ@mail.gmail.com> (raw)
In-Reply-To: <87po8ciy64.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

We had a discussion about that on the irc channel, and it seems, that we
can make a boostrap path to another architecture by using a bootstrapped
toolchain and cross compiling. It is not very confortable, but I think we
can extend the list of bootstrappable software considerably by that.

2017-11-20 19:48 GMT+01:00 Jan Nieuwenhuizen <janneke@gnu.org>:

> Ludovic Courtès writes:
>
> Hey Ludo'
>
> > Also, AIUI, stage0 is i386-specific.  Thoughts on how we can eventually
> > support the other architectures Guix works on?
>
> I goofed ere.  Stage0 is mainly using a VM and it has a x86_64
> prototype; no x86 yet.  Of course, creating the x86 hex0 is almost
> trivial given that 64 bit has been done.
>
> However, the main problem is the gap between hex0 and hex1, hex2.  We
> just ignored this by prototyping hex2 and M2 in C.  hex2 and M2 are
> architecture agnostic.
>
> MesCC currently outputs M2, but only for x86.  I'm confident that if we
> show that x86 works and if we consider it to be of value, then x86_64 is
> just more work.  Other architectures...well, "just" more work ;-)
>
> > Thank you, and congrats on this milestone!
>
> Thanks!
> janneke
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
>
>

[-- Attachment #2: Type: text/html, Size: 2080 bytes --]

  reply	other threads:[~2017-11-20 19:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 22:31 prototyping the full source bootstrap path Jan Nieuwenhuizen
2017-11-20  9:20 ` [bootstrappable] " Ludovic Courtès
2017-11-20 11:42   ` [bootstrappable] " Ricardo Wurmus
2017-11-20 18:41     ` Jan Nieuwenhuizen
2017-11-20 18:48       ` Orians, Jeremiah (DTMB)
2017-11-20 21:55       ` Ludovic Courtès
2017-11-21 12:59         ` Orians, Jeremiah (DTMB)
2017-11-21 17:52           ` Jan Nieuwenhuizen
2017-11-21 18:23             ` Orians, Jeremiah (DTMB)
2017-11-23  4:56               ` Mark H Weaver
2017-11-27 12:42                 ` Orians, Jeremiah (DTMB)
2017-11-23 17:55     ` Jan Nieuwenhuizen
2017-11-23 22:12       ` Ricardo Wurmus
2017-11-25 10:51         ` Jan Nieuwenhuizen
2017-11-20 18:48   ` Jan Nieuwenhuizen
2017-11-20 19:22     ` Gábor Boskovits [this message]
2017-11-20 12:45 ` [bootstrappable] " Orians, Jeremiah (DTMB)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE4v=pgeD1KouSMiEOfHWOQOSfYUbL673Vhj9uCoNDSSLxYNbQ@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=bootstrappable@freelists.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.