From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: [PATCH] Fix jellyfish on non-x86_64 Date: Sun, 28 Feb 2016 18:26:16 +0100 Message-ID: <87d1rgd9vr.fsf@mdc-berlin.de> References: <8760xadti8.fsf@mdc-berlin.de> <20160227233117.GA12075@solar> <87povgdh8r.fsf@mdc-berlin.de> <20160228145241.GA19415@solar> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39861) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aa56z-0005QR-SC for guix-devel@gnu.org; Sun, 28 Feb 2016 12:26:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aa56v-0002Yi-Ra for guix-devel@gnu.org; Sun, 28 Feb 2016 12:26:29 -0500 Received: from venus.bbbm.mdc-berlin.de ([141.80.25.30]:43475) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aa56v-0002Yb-ID for guix-devel@gnu.org; Sun, 28 Feb 2016 12:26:25 -0500 In-Reply-To: <20160228145241.GA19415@solar> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Andreas Enge Cc: guix-devel Andreas Enge 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 archite= cture: >> https://github.com/gmarcais/Jellyfish/issues/52#issuecomment-1713199= 52 >> I don=E2=80=99t know if this fixes the build for i686 and mips. Do yo= u think we >> could apply it and check the build logs for errors then? > > Could you build the package for i686 (I think "--system=3Di686-linux" i= s 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 t= o > par with master...). If it fixes no architecture, then there is not muc= h > 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=E2=80=99t fix the build on i686. I reported this to upstr= eam. Obviously, there=E2=80=99s no use in applying this patch. ~~ Ricardo