From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Update and fix Chicken Scheme.
Date: Mon, 21 Mar 2016 17:35:51 +0100 [thread overview]
Message-ID: <87twjz7pqw.fsf@gnu.org> (raw)
In-Reply-To: <87h9g03irs.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 20 Mar 2016 23:07:51 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> From e2fc4f5bfac95e51ba0494ffccd6354680a73385 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Sun, 20 Mar 2016 17:10:12 +0100
> Subject: [PATCH 1/4] gnu: chicken: Update to 4.10.0.
>
> * gnu/packages/scheme.scm (chicken): Update to 4.10.0.
OK!
> From 98fe76c36134f78346b18f62b09cc1ba42d11dde Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Sun, 20 Mar 2016 17:10:41 +0100
> Subject: [PATCH 2/4] gnu: chicken: Use "modify-phases" syntax.
>
> * gnu/packages/scheme.scm (chicken)[arguments]: Use "modify-phases"
> syntax.
OK.
> From 345d60f91763c5edf696c7e9c27675655423b8e3 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Sun, 20 Mar 2016 23:01:11 +0100
> Subject: [PATCH 3/4] gnu: chicken: Disable port tests.
>
> * gnu/packages/scheme.scm (chicken)[arguments]: Do not run port tests.
OK. I think that’s reasonable. It’s an improvement anyway, and we can
always discuss it with upstream eventually.
> From fd4730fc5cf431d42d9ae670544eb7d6408d78e3 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Sun, 20 Mar 2016 23:03:24 +0100
> Subject: [PATCH 4/4] gnu: chicken: Build with GCC 4.8.
>
> * gnu/packages/scheme.scm (chicken)[native-inputs]: Add GCC 4.8.
OK.
Thank you!
Ludo’.
prev parent reply other threads:[~2016-03-21 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 22:07 [PATCH] Update and fix Chicken Scheme Ricardo Wurmus
2016-03-21 16:35 ` Ludovic Courtès [this message]
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=87twjz7pqw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.