From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: wip-arm Date: Mon, 01 Dec 2014 13:53:55 +0100 Message-ID: <87tx1fcyzg.fsf@gnu.org> References: <20141126162132.GA8669@jocasta.intra> <87fvd4n5lb.fsf@gnu.org> <20141129063742.GA23329@jocasta.intra> 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]:58592) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvQUN-0002T3-ID for guix-devel@gnu.org; Mon, 01 Dec 2014 07:54:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XvQUH-0004Qc-I7 for guix-devel@gnu.org; Mon, 01 Dec 2014 07:54:03 -0500 Received: from hera.aquilenet.fr ([2a01:474::1]:44815) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XvQUH-0004QW-BU for guix-devel@gnu.org; Mon, 01 Dec 2014 07:53:57 -0500 In-Reply-To: <20141129063742.GA23329@jocasta.intra> (John Darrington's message of "Sat, 29 Nov 2014 07:37:42 +0100") 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: John Darrington Cc: guix-devel@gnu.org John Darrington skribis: > On Thu, Nov 27, 2014 at 02:19:44PM +0100, Ludovic Court??s wrote: > John Darrington skribis: >=20=20=20=20=20=20 > > It contains the start of a port to an Arm architecture. Currently > > it hasn't got very far unfortunately. >=20=20=20=20=20=20 > It allow you to cross-build the bootstrap tarballs for ARM, right? >=20=20=20=20=20=20 > > Does anyone know the next step? > > The bootstrap tarballs are insufficient to natively build guix on the tar= get machine. Yes, that=E2=80=99s expected. > And I have been unable to build a version of Guile which is up to the job= - they all > have one problem or another. The machine should already have a working Guile, GCC, libgcrypt, etc. Using the bootstrap tools for that job may fail unexpected. (Since you gave access to your armv7 box, I tried to get Guile running, but haven=E2=80=99t been very far yet. I=E2=80=99ll keep you updated.) > The Porting section in the manual says that I must "update" some files an= d return the "right=20 > name" and that it must be "taught about the new platform". Can anyone el= aborate on this? > How do I know what parts of the files must be updated? Which name is "ri= ght" and how do > I "teach" it about the new platform? Commit 1c0c417d expounds that section a bit. Commit f57ff219a, which added mips64el-linux, should also give you info. Thanks, Ludo=E2=80=99.