From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: wip-arm
Date: Mon, 01 Dec 2014 13:53:55 +0100 [thread overview]
Message-ID: <87tx1fcyzg.fsf@gnu.org> (raw)
In-Reply-To: <20141129063742.GA23329@jocasta.intra> (John Darrington's message of "Sat, 29 Nov 2014 07:37:42 +0100")
John Darrington <john@darrington.wattle.id.au> skribis:
> 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.
Yes, that’s 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’t been very far yet. I’ll keep you updated.)
> 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?
Commit 1c0c417d expounds that section a bit. Commit f57ff219a, which
added mips64el-linux, should also give you info.
Thanks,
Ludo’.
prev parent reply other threads:[~2014-12-01 12:54 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 ` wip-arm John Darrington
2014-12-01 12:53 ` Ludovic Courtès [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
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=87tx1fcyzg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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).