From: Leo Famulari <leo@famulari.name>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 01/15] gnu: chez-scheme: Add search-path and fix i686 build.
Date: Wed, 19 Oct 2016 13:32:44 -0400 [thread overview]
Message-ID: <20161019173244.GF8998@jasmine> (raw)
In-Reply-To: <CAKrPhPP0-P57f9iiXNeNGCvbwiwkjpXEi1O4W2yPhao8=Zuwhg@mail.gmail.com>
On Wed, Oct 19, 2016 at 06:28:45PM +0200, Federico Beffa wrote:
> On Mon, Oct 17, 2016 at 3:34 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> > Hello Federico,
> >
> > Federico Beffa <beffa@ieee.org> skribis:
> >
> >> On Sun, Oct 16, 2016 at 8:25 PM, Ricardo Wurmus <rekado@elephly.net> wrote:
> >> From 7875840eb0f0d0d844da40735faabd10b791f0dd Mon Sep 17 00:00:00 2001
> >> From: Federico Beffa <beffa@fbengineering.ch>
> >> Date: Mon, 17 Oct 2016 09:01:11 +0200
> >> Subject: [PATCH 02/17] gnu: chez-scheme: Fix i686 build.
> >>
> >> * gnu/packages/scheme.scm (chez-scheme): Add 'configure-flags', generalize
> >> 'configure' phase and simplify 'install-doc' phase.
>
> This patch was meant to fix the i686 build, but it looks like it doesn't :-(
>
> The patch adds a 'configure-flags' argument specifying the machine
> type as instructed by Chez '-/configure --help' message. In addition,
> patching of the make files was generalized to recognize compiler flags
> for all architectures (previously it only recognized x86_64 ones).
> However, because I'm short on space I only checked that I didn't break
> the 64bit version and didn't build the 32bit one.
Heh :) I recently dug out my LVM cheat sheet and increased my /gnu/store
capacity by 20 GB. It was worth the 20 minutes of downtime!
prev parent reply other threads:[~2016-10-19 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 15:31 [PATCH 01/15] gnu: chez-scheme: Add search-path and fix i686 build Federico Beffa
2016-10-16 18:25 ` Ricardo Wurmus
2016-10-17 7:15 ` Federico Beffa
2016-10-17 13:34 ` Ludovic Courtès
2016-10-19 16:28 ` Federico Beffa
2016-10-19 17:32 ` Leo Famulari [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=20161019173244.GF8998@jasmine \
--to=leo@famulari.name \
--cc=beffa@ieee.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.