From: Efraim Flashner <efraim@flashner.co.il>
To: Gabriel Wicki <gabriel@erlikon.ch>
Cc: guix-devel@gnu.org
Subject: Re: RISCV porting effort
Date: Thu, 10 Jun 2021 16:22:48 +0300 [thread overview]
Message-ID: <YMISKC60rGggYAT7@3900XT> (raw)
In-Reply-To: <20210608222822.fu4f2kcbtvt6o6hc@silver>
[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]
On Wed, Jun 09, 2021 at 12:28:22AM +0200, Gabriel Wicki wrote:
> Hello everyone!
>
> > Efraim Flashner <efraim@flashner.co.il> skribis:
> > > Porting Guix comes with two parts: building the bootstrap-tarballs and
> > > adding support for the new architecture in (gnu packages bootstrap).
> > > Support for riscv was added to GCC with 7.1.0 so I had to bump the
> > > bootstrap GCC to 7 (and adjust some inputs), and guile-2.0.14 didn't
> > > known the endianness of riscv64 so instead of patching it I bumped the
> > > bootstrap guile to 3.0. I uploaded my bootstrap-tarballs to my regular
> > > spot after signing them and switched over to the riscv machine.
>
> Do i understand correctly that the bootstrap-tarballs can be
> cross-compiled and tested (to some extent) in a qemu-system-riscv? Or does
> this *have* to fail (by Guix's design) due to it not being bootstrappable?
>
They get cross compiled from another architecture, using the package
definitions in gnu/packages/make-bootstrap.scm. From what I've seen
online, it should be possible to boot Ubuntu's riscv64 image using qemu.
I haven't tried enabling riscv64 support in my binfmt service and
try building on my main machine.
>
> On Tue, Jun 08, 2021 at 03:43:44PM +0200, Ludovic Courtès wrote:
> > If the HiFive works fine, let me remind you that we have budget to buy
> > hardware, so we could just as well order a couple of these right away
> > (maybe you’ll have Guix System running by the time we receive them ;-)).
> >
> > What we need is someone to order the machine(s) and to host it
> > afterwards, with stable connectivity. This must be agreed upon by the
> > Spending Committee (currently Tobias, Ricardo, and myself; email
> > guix-finance@gnu.org). You’ll then be reimbursed by the FSF, our
> > current fiscal sponsor.
> >
> > Any takers? Or should we wait until you have more experience with
> > yours, Efraim?
> I could see myself doing that. I've been thinking about getting a HiFive
> Unmatched for a while and getting the hardware makes working on it a bit
> more exciting!
>
> Do i understand correctly that this machine would then be used to
> build Guix packages and serve them? I.e. a worker on ci.guix.gnu.org?
>
>
> Have a nice week!
> gabriel
>
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-10 13:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 7:09 RISCV porting effort Efraim Flashner
2021-06-07 15:37 ` Christopher Lemmer Webber
2021-06-08 13:43 ` Ludovic Courtès
2021-06-08 22:28 ` Gabriel Wicki
2021-06-10 13:22 ` Efraim Flashner [this message]
2021-06-11 21:07 ` Ludovic Courtès
2021-06-10 13:20 ` Efraim Flashner
2021-06-11 22:07 ` Ludovic Courtès
2021-06-18 13:05 ` RISCV porting effort (now in stock @mouser) Gabriel Wicki
2021-06-11 11:16 ` RISCV porting effort Efraim Flashner
2021-06-13 17:24 ` Vagrant Cascadian
2021-06-14 7:27 ` Efraim Flashner
2021-06-15 1:00 ` Vagrant Cascadian
2021-06-15 12:37 ` Efraim Flashner
2021-06-13 21:21 ` Christopher Baines
2021-06-20 15:37 ` Ludovic Courtès
2022-06-16 1:46 ` Pjotr Prins
2022-06-16 18:12 ` Maxim Cournoyer
2022-06-17 16:08 ` Ludovic Courtès
2022-06-17 22:52 ` Pjotr Prins
2022-06-20 7:45 ` Pjotr Prins
2022-06-22 13:37 ` Ludovic Courtès
2022-06-22 15:19 ` Ekaitz Zarraga
2022-06-28 8:54 ` Efraim Flashner
2022-06-30 12:01 ` Ludovic Courtès
2022-07-03 9:07 ` Efraim Flashner
2022-06-24 6:37 ` Pjotr Prins
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=YMISKC60rGggYAT7@3900XT \
--to=efraim@flashner.co.il \
--cc=gabriel@erlikon.ch \
--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.