From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH] gnu: Add mash. Date: Sat, 10 Sep 2016 17:20:59 -0400 Message-ID: <20160910212059.GA7137@jasmine> References: <87h9a2yweu.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> <20160831194426.GC22495@jasmine> <87zinsae3u.fsf@elephly.net> <87shtkq6rc.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> <20160906210127.GB1089@jasmine> <87eg4urqq3.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60902) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bipi6-0005I5-8P for guix-devel@gnu.org; Sat, 10 Sep 2016 17:21:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bipi3-0002yj-0G for guix-devel@gnu.org; Sat, 10 Sep 2016 17:21:14 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:35824) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bipi1-0002uU-0m for guix-devel@gnu.org; Sat, 10 Sep 2016 17:21:10 -0400 Content-Disposition: inline In-Reply-To: <87eg4urqq3.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> 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" To: Marius Bakke Cc: guix-devel@gnu.org On Thu, Sep 08, 2016 at 11:06:44PM +0100, Marius Bakke wrote: > Leo Famulari writes: > > > On Thu, Sep 01, 2016 at 11:00:39AM +0100, Marius Bakke wrote: > >> I had these in inputs initially and was surprised to see no references. > >> Both seems to be compiled into the final program[0]: when running "mash > >> info" on an invalid file (the provided data/refseq.msh), a generic > >> capnproto exception is thrown (src/capnp/serialize.c++:159). > > > > I wonder, does using native-inputs work when building mash for another > > architecture? > > That's interesting, the package indeed fails to build on i686. Do you mean that it fails when you try to build from x86_64 using `guix build --system=i686-linux`? I wondered if that particular case would work since the packages that are native-inputs would only be built for the architecture of the builder, if I understand correctly.