all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guile 3 migration plan
Date: Sun, 19 Jan 2020 22:29:09 +0100	[thread overview]
Message-ID: <87tv4rqgnu.fsf@gnu.org> (raw)
In-Reply-To: <871rrxycs5.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 17 Jan 2020 22:48:58 +0100")

Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

>>      Once we’re done, we can change (guix self) so that ‘guix pull’
>>      pulls Guix on Guile 3.
>
> The attached patch does that, I tested it with “make as-derivation”.
> I’ll do some more testing but unless I’m overlooking something, we can
> apply it anytime now.

The showstopper is that currently “guile3.0-guix” doesn’t build on all
arches:

  https://ci.guix.gnu.org/search?query=guile3.0-guix

On AArch64, it’s test failures (that needs to be investigated, but I
suspect it’s nothing serious.)

However, on ARMv7, Guile 3.0 segfaults as it’s building:

  https://ci.guix.gnu.org/log/8b8c0hxvm9qa5kff168vdr3943cc2s61-guile-next-3.0.0

That needs more work!

Ludo’.

  reply	other threads:[~2020-01-19 21:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 10:08 Guile 3 migration plan Ludovic Courtès
2020-01-16 13:57 ` zimoun
2020-01-16 14:57 ` Efraim Flashner
2020-01-16 17:23   ` Ludovic Courtès
2020-01-16 17:58 ` Vagrant Cascadian
2020-01-17 21:43   ` Ludovic Courtès
2020-01-17 21:48 ` Ludovic Courtès
2020-01-19 21:29   ` Ludovic Courtès [this message]
2020-01-20 17:11     ` Ludovic Courtès
2020-01-23 16:39       ` Ludovic Courtès
2020-01-23 22:25         ` Ricardo Wurmus
2020-01-24  9:29           ` Ludovic Courtès
2020-01-25 17:37             ` Ludovic Courtès
2020-01-25 19:03               ` Ricardo Wurmus
2020-01-28 10:26                 ` Ludovic Courtès

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=87tv4rqgnu.fsf@gnu.org \
    --to=ludo@gnu.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.