all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Fix jellyfish on non-x86_64
Date: Sun, 28 Feb 2016 18:26:16 +0100	[thread overview]
Message-ID: <87d1rgd9vr.fsf@mdc-berlin.de> (raw)
In-Reply-To: <20160228145241.GA19415@solar>


Andreas Enge <andreas@enge.fr> writes:

> On Sun, Feb 28, 2016 at 03:47:16PM +0100, Ricardo Wurmus wrote:
>> Possibly, but the author would like it to run on more than one architecture:
>>   https://github.com/gmarcais/Jellyfish/issues/52#issuecomment-171319952
>> I don’t know if this fixes the build for i686 and mips.  Do you think we
>> could apply it and check the build logs for errors then?
>
> Could you build the package for i686 (I think "--system=i686-linux" is the
> magic option)? And maybe Mark could test it on one of the mips (mine is so
> slow that I unplugged it; it would probably take a few days to get up to
> par with master...). If it fixes no architecture, then there is not much
> use in applying it (but also no harm; so as it will probably make
> communication with the author easier if you can point to build logs,
> why not apply it finally).

Yeah, it doesn’t fix the build on i686.  I reported this to upstream.
Obviously, there’s no use in applying this patch.

~~ Ricardo

      reply	other threads:[~2016-02-28 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 16:10 [PATCH] Fix jellyfish on non-x86_64 Ricardo Wurmus
2016-02-27 20:22 ` Efraim Flashner
2016-02-27 21:02   ` Ricardo Wurmus
2016-02-27 23:31 ` Andreas Enge
2016-02-28 14:47   ` Ricardo Wurmus
2016-02-28 14:52     ` Andreas Enge
2016-02-28 17:26       ` Ricardo Wurmus [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=87d1rgd9vr.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=andreas@enge.fr \
    --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.