unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "bug-guix@gnu.org" <bug-guix@gnu.org>,
	"Andrius Štikonas" <andrius@stikonas.eu>,
	"efraim@flashner.co.il" <efraim@flashner.co.il>,
	"Jan Nieuwenhuizen" <janneke@gnu.org>,
	"guix-devel\\@gnu.org" <guix-devel@gnu.org>
Subject: Bootstrapping path discovered for RISC-V 64bit
Date: Wed, 3 Jul 2024 17:16:55 +0200	[thread overview]
Message-ID: <26411bab-0d65-dc55-e55d-7d0a0c96de50@elenq.tech> (raw)

Hi,

Thanks to NlNet we have found a bootstrapping path for RISC-V 64 and we 
created an alternative `commencement.scm` draft that builds from source 
up to a GCC-9.

At the moment, that GCC-9 does not provide C++ support in my Guix 
packages. I tried to add it but I had issues. We made it work for 
live-bootstrap (Andrius did), and now it's time to move that to Guix but 
it's getting a little bit difficult with GCC's build-system.

I'm opening this issue to make the handover to Guix. I have already 
worked with Efraim and he agreed to continue with this work until it's 
upstreamed. Also Janneke is working on a version of this commencement 
module that adds support for x86, so we could use that for everything 
instead of relying in two different bootstrapping paths.

This will take some time to integrate. There are a couple of packages 
that I didn't bootstrap yet (but it's possible to bootstrap them): 
`flex` and `bison`. Mostly because we wanted to fix 
<https://issues.guix.gnu.org/52311>, too.

The Gash package is replaced with a non-bootstrapped Bash because 
there's an issue in Gash that hangs the bootstrapping process. We have 
reported it upstream. We should use Gash once the issue is fixed.

Also, we only made the path until a modern GCC, not all the rest of it, 
that we should be able to reuse from the current `commencement.scm` module.

This is the link to the repo:

https://github.com/ekaitz-zarraga/commencement.scm

I'm more than open to help Guix include the RISC-V bootstrapping process 
upstream, so if you have any question, suggestion or anything else, feel 
free to directly contact me.

As a note, in this series of blogposts I shared the 2 year process until 
today, and almost everything is documented:

https://ekaitz.elenq.tech/tag/bootstrapping-gcc-in-risc-v.html

Also, I'd like to publicly thank everyone who took part in this process. 
Especially Andrius, for all those sleepless nights we spent fixing weird 
compiler errors.

Let's make this finally happen!

Ekaitz



                 reply	other threads:[~2024-07-03 15:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=26411bab-0d65-dc55-e55d-7d0a0c96de50@elenq.tech \
    --to=ekaitz@elenq.tech \
    --cc=andrius@stikonas.eu \
    --cc=bug-guix@gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).