unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: guix-devel@gnu.org
Subject: Re: wip-arm
Date: Sat, 29 Nov 2014 07:37:42 +0100	[thread overview]
Message-ID: <20141129063742.GA23329@jocasta.intra> (raw)
In-Reply-To: <87fvd4n5lb.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On Thu, Nov 27, 2014 at 02:19:44PM +0100, Ludovic Court??s wrote:
     John Darrington <john@darrington.wattle.id.au> skribis:
     
     > It contains the start of a port to an Arm architecture.  Currently
     > it hasn't got very far unfortunately.
     
     It allow you to cross-build the bootstrap tarballs for ARM, right?
     

Does anyone know the next step?

The bootstrap tarballs are insufficient to natively build guix on the target machine.
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 Porting section in the manual says that I must "update" some files and return the "right 
name" and that it must be "taught about the new platform".  Can anyone elaborate on this?
How do I know what parts of the files must be updated?  Which name is "right" and how do
I "teach" it about the new platform?

J'


-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2014-11-29  6:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 16:21 wip-arm John Darrington
2014-11-27 13:19 ` wip-arm Ludovic Courtès
2014-11-27 14:09   ` wip-arm John Darrington
2014-11-29  6:37   ` John Darrington [this message]
2014-12-01 12:53     ` wip-arm Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141129063742.GA23329@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).