From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: [bootstrappable] Re: prototyping the full source bootstrap path Date: Mon, 20 Nov 2017 20:22:10 +0100 Message-ID: References: <877eulkii1.fsf@gnu.org> <87y3n15mru.fsf@gnu.org> <87po8ciy64.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c0b9c9cc9962a055e6f00ec" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49520) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eGre2-0002un-SW for guix-devel@gnu.org; Mon, 20 Nov 2017 14:22:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eGre1-0003OL-QZ for guix-devel@gnu.org; Mon, 20 Nov 2017 14:22:14 -0500 In-Reply-To: <87po8ciy64.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: bootstrappable@freelists.org Cc: Guix-devel --94eb2c0b9c9cc9962a055e6f00ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 : > Ludovic Court=C3=A8s 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 | GNU LilyPond http://lilypond.org > Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.c= om > > --94eb2c0b9c9cc9962a055e6f00ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 1= 9:48 GMT+01:00 Jan Nieuwenhuizen <janneke@gnu.org>:
Ludovic Court=C3=A8s writes:

Hey Ludo'

> Also, AIUI, stage0 is i386-specific.=C2=A0 Thoughts on how we can even= tually
> support the other architectures Guix works on?

I goofed ere.=C2=A0 Stage0 is mainly using a VM and it has a x86_64<= br> prototype; no x86 yet.=C2=A0 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.=C2=A0 We<= br> just ignored this by prototyping hex2 and M2 in C.=C2=A0 hex2 and M2 are architecture agnostic.

MesCC currently outputs M2, but only for x86.=C2=A0 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.=C2=A0 Other architectures...well, "just" more wor= k ;-)

> 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=C2=AE http://AvatarAcademy.c= om


--94eb2c0b9c9cc9962a055e6f00ec--